Re: Tracker bugs and our release process

2017-08-15 Thread Mark Atwood via devel
I have read ESR's writeup on our buglist, and agree with his assessments. ..m On Tue, Aug 15, 2017 at 5:27 AM Hal Murray via devel wrote: > > * I need to work on #348: reverse function for restrict > > * unpeer should be made to fully work from ntpq :config. This one is > mine too. > > There i

Re: Tracker bugs and our release process

2017-08-15 Thread Hal Murray via devel
> * I need to work on #348: reverse function for restrict > * unpeer should be made to fully work from ntpq :config. This one is mine > too. There is a quirk tangled in this area. I don't know if there is a bug for it. When the pool mode adds a server, if needed, it pokes a hole in the restri

Re: #251: Add fudge option to server config (was: Tracker bugs and our release process)

2017-08-14 Thread Gary E. Miller via devel
Yo Achim! On Mon, 14 Aug 2017 18:24:16 +0200 Achim Gratz via devel wrote: > I've ran at around 1.5…2.0ms excess upstream delay for the last few > years (VDSL2) and had to shift the GPS chimers accordingly in order to > allow reasonably smooth client fallback from internal to external > sync. Th

#251: Add fudge option to server config (was: Tracker bugs and our release process)

2017-08-14 Thread Achim Gratz via devel
Eric S. Raymond via devel writes: > #251: Add fudge option to server config > https://gitlab.com/NTPsec/ntpsec/issues/251 > > Gary and Daniel are having an argument over whether this is a good > idea. The general idea of allowing NTP to compensate for asymmetric network delays is sound, I think.

Tracker bugs and our release process

2017-08-14 Thread Eric S. Raymond via devel
I've spent the last week triaging and resolving items from the NTPsec issue tracker. We're making excellent progress; the count of unresolved issues has gone from 41 to 15. I shall round up the remaining issues and discuss where I think our priorities need to be. Summary: * I need to work on #3