Hi, On Tue, 06.07.2010 at 00:11:26 -0400, William Yodlowsky <[email protected]> wrote: > 3.0 won't be upgraded any more, which is why -current has 3.6 in its > place.
ok - I've yesterday seen an empty 3.6 directory, but at least a working 3.5 directory. 4.7 ships with 3.0.18, though. > Even Firefox 3.5 is deprecated. I am working on a diff to 3.5.10 > without the nss/nspr changes and it will be done next. Thank you for the effort, although this won't affect me at all. > As for nginx, there was fallout from the move to 0.7.67... it broke > ruby-passenger. As there wasn't a strong reason to move -stable to > 0.7.67 and thus cost ruby-passenger users an upgrade, I decided to wait > on the update. Ok. > Are your systems affected by any of the bugs resolved in the newer > nginx? I was seeing not-very-smooth operation of MTOS and thought I'd give it a whirl, but then got drowned in other work. But at this point, this is only a fuzzy feeling, not hard facts. So far I have moved several servers to 0.7.67 and not seen any downsides, but I guess I might hit the Ruby problem before long... -- Kind regards, --Toni++
