[ntpsec commit] Update the TODO.
Eric S. Raymond
esr at ntpsec.org
Tue Oct 20 19:21:06 UTC 2015
Module: ntpsec
Branch: master
Commit: 79058aeb0de69ef534a9aff53a78dd5f3809739a
Changeset: http://git.ntpsec.org/ntpsec/commit/?id=79058aeb0de69ef534a9aff53a78dd5f3809739a
Author: Eric S. Raymond <esr at thyrsus.com>
Date: Tue Oct 20 15:20:56 2015 -0400
Update the TODO.
---
devel/TODO | 30 +++++++++---------------------
1 file changed, 9 insertions(+), 21 deletions(-)
diff --git a/devel/TODO b/devel/TODO
index 39972ab..059a4d4 100644
--- a/devel/TODO
+++ b/devel/TODO
@@ -45,7 +45,8 @@ None right now. (Sep-22 2015)
* We need a build time option to disable all dangerous operations
that ntpq can produce. First we need to enumerate them.
-* systime.c needs patching to put ntpdsim's hook back in place.
+* systime.c needs patching to put ntpdsim's hook back in place. Deferred
+ until the ntpdsim build is fixed.
* ntpfrob -c behaves mysteriously. Someone with domain knowledge (probably Hal)
should review the code.
@@ -61,36 +62,23 @@ None right now. (Sep-22 2015)
* Build testing. The build/CI farm needs to be fully operational.
-* Live testing. Somebody needs to take the development branch,
-build it on a real machines, and live-test it to make sure that
-it issues sane corrections and doesn't core-dump or barf.
-We need to do that on various platforms.
-
-* We also need to live-test various refclocks. It would be nice
-to test the full matrix of refclock x platform, but that's too
-much work. We should probably test as many refclocks as we can
-on at least one platform and test the NMEA, Atom, and SHM drivers
-on most platforms.
+* We need to live-test various refclocks. It would be nice
+ to test the full matrix of refclock x platform, but that's too
+ much work. We should probably test as many refclocks as we can
+ on at least one platform and test the NMEA, Atom, and SHM drivers
+ on most platforms.
* We need to live-test leap seconds, both getting them from a file
-with ntpleapfetch and getting them from other NTP servers.
+ with ntpleapfetch and getting them from other NTP servers.
* The script tests in scripts/t should be investigated, perhaps
-they are salvageable.
+ they are salvageable.
=== Documentation ===
* Short doc on how to tell your ntpd is running correctly.
Perhaps lifted from GPSD Time Service HOWTO?
-* These manpages have no corresponding material inside docs/. Is that OK?
-
- ntpd/ntp.keys.txt
- scripts/calc_tickadj/calc_tickadj.txt
- scripts/summary.txt
- scripts/ntpsweep/ntpsweep.txt
- scripts/plot_summary.txt
-
* The format and organization of the NEWS file needs a rethink.
* Phabricator-centered workflow needs to be written up and integrated
More information about the vc
mailing list