<div dir="ltr"><div>Hi,</div><div><br></div><div>I would dearly love to see #204 (/etc/ntp.d) be included in 1.0. <br></div><div><br></div><div>As a SysAdm, I typically read the new features list rarely. If it does not land in 1.0 (and pacakge managers and I do not start using it then), it may never get used.</div><div><br></div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature">-- <br>Sanjeev Gupta<br>+65 98551208 <a href="http://www.linkedin.com/in/ghane" target="_blank">http://www.linkedin.com/in/ghane</a></div></div>
<br><div class="gmail_quote">On Wed, Aug 23, 2017 at 10:07 PM, Eric S. Raymond via devel <span dir="ltr"><<a href="mailto:devel@ntpsec.org" target="_blank">devel@ntpsec.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Our planned ship date for 1.0 is 28 September.<br>
<br>
We'll feature-freeze sooner than that - not sure when yet but<br>
somewhere in the ballpark of 7-14 September seems likely.<br>
<br>
We're down to 7 issues on the tracker. Feature freeze has<br>
implications for the two that are RFEs, and for one other.<br>
Here they are:<br>
<br>
#251: Add fudge option to server config<br>
<br>
If this is going to happen in 1.0. somebody needs to land a patch<br>
before feature freeze. That someone should be equipped to test the<br>
patch - e.g. not me, as I don't have significant asymmetric delay<br>
to contend with.<br>
<br>
If someone steps up, though, I will write the scanner/parser end to<br>
get that offset number into the peer structure. It's not reasonable<br>
to expect anyone else but me to grapple with *that* part of the code.<br>
<br>
Remember, documentation patches *are* required when you add a feature<br>
<br>
As this would be a pure feature addition, there's no issue with<br>
allowing it to wait until 1.1.<br>
<br>
#204: Support /etc/ntp.d<br>
<br>
This feature is working, and documented - has been for more than 6<br>
months. For pretty obvious reasons, we should not go breaking<br>
backward compatibility after 1.0.<br>
<br>
That means the window during which we can change the behavior is<br>
getting pretty short. Anybody who wants this has two to three<br>
weeks, at the outside, to make the argument and ship the code.<br>
<br>
When I say "make the argument" I mean that I want to see a concrete<br>
design and an explanation of why it solves all the problems this one<br>
does, and one or more additional ones. Merely not liking it the way<br>
it is insufficient.<br>
<br>
#55: ntpd refclock GPSD_JSON just stops working.<br>
<br>
I am unhappy with this driver. I believe - as this bug demonstrates -<br>
that it's too crappy to ship if we want to establish and maintain a<br>
reputation for trouble-free operation.<br>
<br>
It's an unusual case - the feature that brings it closest to working<br>
right is marked experimental, and it's redundant with the SHM driver<br>
because GPSD feeds the SHM driver quite happily. In fact, the JSON<br>
parsing overhead means the latency and jitter of this driver is<br>
necessarily inferior to delivery via SHM.<br>
<br>
Thus, I think the best thing to do about it would be do simply delete it<br>
and shed the defect exposure, redirecting users to GPSD+SHM. And<br>
if that going to happen, it needs to happen *now* - that is, before<br>
1.0 implies a promise that it will be stable and maintained.<br>
<br>
If any of you have an interest in saving this driver, step up now<br>
and fix it.<br>
--<br>
<a href="<a href="http://www.catb.org/~esr/" rel="noreferrer" target="_blank">http://www.catb.org/~<wbr>esr/</a>">Eric S. Raymond</a><br>
<br>
"As to the species of exercise, I advise the gun. While this gives [only]<br>
moderate exercise to the body, it gives boldness, enterprise, and independence<br>
to the mind. Games played with the ball and others of that nature, are too<br>
violent for the body and stamp no character on the mind. Let your gun,<br>
therefore, be the constant companion to your walks."<br>
-- Thomas Jefferson, writing to his teenaged nephew.<br>
______________________________<wbr>_________________<br>
devel mailing list<br>
<a href="mailto:devel@ntpsec.org">devel@ntpsec.org</a><br>
<a href="http://lists.ntpsec.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.ntpsec.org/<wbr>mailman/listinfo/devel</a><br>
</blockquote></div><br></div>