Re: Trying again: prep for 1.0.1

devel@ntpsec.org said: > What kind of special labeling does ntpsnmpd require? Is putting > "experimental" in the documentation sufficient? Does it need to give a > warning on launch? I'd put "experimental" in NEWS. If you put something in the documentation it should probably say a bit about

Re: Trying again: prep for 1.0.1

Matthew Selsky : > On Fri, Mar 09, 2018 at 03:25:02PM -0500, Eric S. Raymond via devel wrote: > > Eric S. Raymond via devel : > > > The CVEs we dodged aught to be listed in NEWS. For bragging purposes. > > > > I have just done this. > > Have we

Re: Trying again: prep for 1.0.1

On Fri, Mar 09, 2018 at 03:25:02PM -0500, Eric S. Raymond via devel wrote: > Eric S. Raymond via devel : > > The CVEs we dodged aught to be listed in NEWS. For bragging purposes. > > I have just done this. Have we committed the fix for the CVE that we didn't dodge? Thanks,

Re: Trying again: prep for 1.0.1

Eric S. Raymond via devel : > The CVEs we dodged aught to be listed in NEWS. For bragging purposes. I have just done this. -- http://www.catb.org/~esr/;>Eric S. Raymond My work is funded by the Internet Civil Engineering Institute: https://icei.org Please visit

Re: Trying again: prep for 1.0.1

Matthew Selsky via devel : > Can we please call this release 1.1 since it's not just a minor patch from > 1.0? We've fixed a lot of things since 1.0 Concur. -- http://www.catb.org/~esr/;>Eric S. Raymond My work is funded by the Internet Civil Engineering

Re: Trying again: prep for 1.0.1

Ian Bruene via devel : > What kind of special labeling does ntpsnmpd require? Is putting > "experimental" in the documentation sufficient? Does it need to give a > warning on launch? That's not normal practice. Just mark it "Experimental" in the documentation. --

Re: Trying again: prep for 1.0.1

Can we please call this release 1.1 since it's not just a minor patch from 1.0? We've fixed a lot of things since 1.0 Thanks, -Matt On Fri, Mar 09, 2018 at 06:43:47PM +, Mark Atwood, Project Manager via devel wrote: > Ok, trying again. We held the 1.0.1 release for a fix for a problem

Re: Trying again: prep for 1.0.1

On 03/09/2018 12:43 PM, Mark Atwood, Project Manager via devel wrote: Ok, trying again.  We held the 1.0.1 release for a fix for a problem that Hal discovered and fixed.  Thank you, Hal! Since we have a CVE fix in this release, and also a "make it work better on AWS AMIs" fix in, I do want

Trying again: prep for 1.0.1

Ok, trying again. We held the 1.0.1 release for a fix for a problem that Hal discovered and fixed. Thank you, Hal! Since we have a CVE fix in this release, and also a "make it work better on AWS AMIs" fix in, I do want to get this release out soonest. Please chime in, is there any reason to