James, I am not sure on the time frame to patch and merge the issues you mentioned, but I am concerned about the change to the behaviour of NTS.
We are not short of integers, 1.3.0 can be next week :-) On Sat, 24 Aug 2019, 3:27 AM James Browning via devel, <devel@ntpsec.org> wrote: > On Fri, Aug 23, 2019 at 9:43 AM Sanjeev Gupta via devel <devel@ntpsec.org> > wrote: > >> We need a point release. Significant things that have happened recently: >> >> >> - The g and G suffixes >> - Removal of neoclock4x >> - Some doc changes >> - The ALPN change >> >> The last is critical, it throws into doubt all the interop we have with >> other NTS implementations. We need a tag to describe our implementation, >> so that we can test again. >> >> Please note only the first point above is captured in the NEWS file. >> > > On a less joking note. > AFAICT issues 599 and 566 still affect FreeBSD. > My current merge requests can wait. > There is a stub in devel/README mentioning devel/tidy which never made it > into the tree. > Is there time to add an IPv4 only initialization option for NTS? > I think we should have hit 1.2.0 earlier but meh. > _______________________________________________ > devel mailing list > devel@ntpsec.org > http://lists.ntpsec.org/mailman/listinfo/devel >
_______________________________________________ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel
