On Sat, Dec 20, 2014 at 01:41:43PM +0000, Harlan Stenn wrote:
> There is, in general, nothing "unstable" about 4.2.7. I wrote that
> before, but you seem to have ignored it. There hasn't been anything
> unstable about 4.2.7 in a long time. What has been blocking 4.2.8 are
> some pesky bugs in relatively unused corners of the code.
Just to add to this:
I've got several servers in the pool, collectively handling
a couple hundred thousand chimes per second, all of which were running
various 4.2.7 patchlevels until this release.
My experience with 4.2.7pXXX is that it hasn't been any more
buggy than 4.2.6. The bugs may be different, that's all, but overall
stability has not been a problem.
Given this, I'm not sure what the point of trying to keep 4.2.6
on life support would be. Even 4.2.7 is usable, and has been for quite
some time, so if it's time for 4.2.8, bring on 4.2.8 -- this might get
a lot of distributions out there that still ship 4.2.6p5 moving.
Cheers,
--msa
_______________________________________________
pool mailing list
[email protected]
http://lists.ntp.org/listinfo/pool
