The goal of 2.8 was to create an Apache-licensed version of 2.6,
which is necessary for the incubation process.
So there really isn't that much functional difference between 2.6 and
2.8. Lots of bugfixes mainly, and some changes in the auth stuff,
and some enhancements in the UI (like section editing).
If 2.6 is working for you, then great! There is *no* need to upgrade
to the latest version (I personally still run Tomcat 5.5 in quite a
few places). However, our support for 2.6 (= Janne's interest to
make bug fixes for 2.6) will be pretty much terminated after 2.8 goes
stable (barring some major security issues) - but if there is a
person who wants to start maintaining 2.6, it'd be great!
Besides, 2.6 was released over six months ago. I think a major
release twice a year is not very fast.
Personally, I think that the fact that we can bring in new
developers, and have those people contribute to the code base in a
rapid cycle is very valuable.
/Janne
On 29 Jun 2008, at 17:50, Terry Steichen wrote:
Yeah, well I'm still scrubbing 2.6.2. You're making my head spin. I
think we're churning out new code and new features much faster than
users can really assimilate it. I'd like things to settle down more
between versions if we want production-quality code that's not largely
obsolete (and unsupported) by the time it's deployed.
Just my $0.02
On Sun, 2008-06-29 at 14:43 +0300, Janne Jalkanen wrote:
BTW, I think that 2.8 is ripe for an alpha release. Any objections
if we start the alpha/beta cycle for 2.8 now? That way we would have
something for people to test and mature.
/Janne
