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 not release?
I'm targeting Tuesday the 13th of March.

..m

On Tue, Feb 20, 2018 at 6:41 PM Mark Atwood <mark.atw...@ntpsec.org> wrote:

> Hi!
>
> A few months ago, I announced prep for a 1.0.1 release.  Turns out, it
> never actually happened.
>
> So, I'm declaring an intention for the 1.0.1 release the weekend after
> next, about March 3rd.
>
> As you work, consider stability, and avoid introducing instability.   And
> let us know if it shouldn't happen.
>
> Thanks, everyone!
>
> ..𐑠𐑸𐑒
> Mark Atwood <mark.atw...@ntpsec.org>
> Project Manager of the NTPsec Project
> +1-206-604-2198 <(206)%20604-2198>
>
-- 

Mark Atwood
http://about.me/markatwood
+1-206-604-2198
_______________________________________________
devel mailing list
devel@ntpsec.org
http://lists.ntpsec.org/mailman/listinfo/devel

Reply via email to