<p dir="ltr">we need to be packaged for debian, rasbian, ubuntu, gentoo, redhat, and suse for 1.0 and be working towards getting into their distribution system (apt, yum, etc)</p>
<br><div class="gmail_quote"><div dir="ltr">On Wed, Oct 5, 2016, 6:27 AM Eric S. Raymond <<a href="mailto:esr@thyrsus.com">esr@thyrsus.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Heads up, Mark! Possible strategy and external-relations issues.<br class="gmail_msg">
<br class="gmail_msg">
I think we're no longer very far, technically, from being ready to<br class="gmail_msg">
ship a 1.0 release. This note is to outline what needs to be done,<br class="gmail_msg">
suggest a rough timeframe, and lay out a couple of scenarios.<br class="gmail_msg">
<br class="gmail_msg">
What brought 1.0 over the horizon was successfully landing Daniel's<br class="gmail_msg">
protocol-machine refactoring. There are a couple of rough spots<br class="gmail_msg">
yet - peer mode is busted, MS-SNTP needs to be re-implemented, and<br class="gmail_msg">
we need to make some decisions about broadcast and anycast modes -<br class="gmail_msg">
but there's also no reason to expect that cleanup to take very long.<br class="gmail_msg">
<br class="gmail_msg">
I polished off about a third of the GitLab tracker bugs today; there<br class="gmail_msg">
are just 20 issues left on the tracker, all pretty routine-looking<br class="gmail_msg">
stuff. I think these can be done between and around major tasks.<br class="gmail_msg">
<br class="gmail_msg">
Here's what I think we ought to do next:<br class="gmail_msg">
<br class="gmail_msg">
* Fix symmetric-peer mode and MS-SNTP, definitely.<br class="gmail_msg">
<br class="gmail_msg">
* Drop broadcast client mode, wich Daniel rightly notes is<br class="gmail_msg">
fundamentally impossible to secure<br class="gmail_msg">
<br class="gmail_msg">
* Fix broadcast server mode, because Mark says a lot of Windows client<br class="gmail_msg">
users rely on it, but add a strong warning that it's a bad idea and<br class="gmail_msg">
users should transition out ASAP.<br class="gmail_msg">
<br class="gmail_msg">
I don't understand "anycast" well enough to have a strong opinion.<br class="gmail_msg">
Does anyone else? Is there any field evidence of use?<br class="gmail_msg">
<br class="gmail_msg">
If we want to ship 1.0 fast, the right thing to do go into soft code<br class="gmail_msg">
freeze after the cleanup, test for a some time, and ship. We could, I<br class="gmail_msg">
think, reasonably expect to ship late October or early November.<br class="gmail_msg">
Let's call this "Case Red".<br class="gmail_msg">
<br class="gmail_msg">
If we're in less of a hurry, the next logical point to freeze is after<br class="gmail_msg">
landing the new restriction language. If we split this up logically,<br class="gmail_msg">
with me writing the config grammar and Daniel the internal primitive(s) for the<br class="gmail_msg">
rules tables and evaluation, this isn't a big job either, nor one<br class="gmail_msg">
paricularly difficult to test. I'd say another three weeks should<br class="gmail_msg">
do it easily. Let's call this "Case Green".<br class="gmail_msg">
<br class="gmail_msg">
If we're not in a hurry at all, then the *next* logical target is<br class="gmail_msg">
moving ntpq all the way to Python. Not a really difficult job, but<br class="gmail_msg">
a largish and somewhat messy one. I'm going to say four weeks.<br class="gmail_msg">
Let's call that "Case Blue".<br class="gmail_msg">
<br class="gmail_msg">
Case Blue would leave us ready to ship 1.0 right around the end of the<br class="gmail_msg">
year.<br class="gmail_msg">
<br class="gmail_msg">
Which should we aim for? Have I missed anything serious? Discuss...<br class="gmail_msg">
--<br class="gmail_msg">
<a href="<a href="http://www.catb.org/~esr/" rel="noreferrer" class="gmail_msg" target="_blank">http://www.catb.org/~esr/</a>">Eric S. Raymond</a><br class="gmail_msg">
<br class="gmail_msg">
Everything you know is wrong. But some of it is a useful first approximation.<br class="gmail_msg">
_______________________________________________<br class="gmail_msg">
devel mailing list<br class="gmail_msg">
<a href="mailto:devel@ntpsec.org" class="gmail_msg" target="_blank">devel@ntpsec.org</a><br class="gmail_msg">
<a href="http://lists.ntpsec.org/mailman/listinfo/devel" rel="noreferrer" class="gmail_msg" target="_blank">http://lists.ntpsec.org/mailman/listinfo/devel</a><br class="gmail_msg">
</blockquote></div>