Janne,
I think Terry's point should probably be taken fairly to heart. While
it's great that the project can move forward quickly, even your most
devoted developers (myself included) don't generally sound like they're
keeping up with the rate of change -- I certainly am not -- witnessed
by the fact that almost nobody has even *looked* at some of the new
features, e.g., work flows. I would also like to have JSPWiki settle
into a period of consolidation to get basically all the foundation
code (events, plugins, AAA, workflow, page management, etc.) solidified
before we jump forward into the next stage.
I look at the cvs directory and it's got a LOT of sub-project and
branch directories that I know nothing about. I hope I'm unusual in
that regard.
I'm probably chomping at the bit as much as anyone for some of the new
features (priha in particular) but by the same token I can't keep up
either with all the releases. I know that when some of those features
come to fruition I'm going to have an enormous amount of work in
refactoring all my own code to be compatible with the new stuff, so
you'll probably see me go to ground even more than recently, simply
trying to keep up. A change to JSPWiki's code can have profound
consequences for those of us who've built systems or sites around it.
And yes, some of us *could* be using older releases but in my case
at least I generally am using as recent a release as is stable given
the bug fixes and compatibility with my own code.
A hopefully gentle request to slow down a bit.... :-)
Murray
Janne Jalkanen wrote:
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
--
...........................................................................
Murray Altheim <murray07 at altheim.com> === = =
http://www.altheim.com/murray/ = = ===
SGML Grease Monkey, Banjo Player, Wantanabe Zen Monk = = = =
Boundless wind and moon - the eye within eyes,
Inexhaustible heaven and earth - the light beyond light,
The willow dark, the flower bright - ten thousand houses,
Knock at any door - there's one who will respond.
-- The Blue Cliff Record
