Ralph Goers wrote:
Reinhard Poetz wrote:
Antonio Gallardo wrote:
yes, as discussed twenty times or so, we can't change the minimum JDK
version for 2.1.x as it's only a patch level release. As 2.1.8 will be
our last 2.1.X release, the days of JDK1.3 and the PITA of maintaining
two branches are counted though :-)
I don't share your optimism that 2.1.8 will be the last 2.1 release.
Realistically, we need to create a 2.2 branch that is stable (most
likely, this just means not bringing in the OSGi stuff) and then release
a couple of versions before it can really be called stable and we can
move on from 2.1. If we go back to the "release often" philosophy then
I would expect at least a 2.1.9 release at the end of the year at the
same time as a second or third 2.2 release.
While I agree that 2.1.8 won't be the last, I'm hoping that it will be
the last of a kind. We've done this before, when 2.1 came out, and we
were maintaining 2.0. As soon as we release 2.2, people will start
exploring it, and, increasingly, development will happen there. Some
things will be backported, and some 2.1 specific bugs will be fixed, and
releases will still be required, but these will increasingly be the
maintenance releases they should all along have been. So let's say,
2.1.8 will hopefully be the last 'major' 2.1.X release.
There's an idealistic hope going on there that, whilst completely
unrealistic, still has some value - unless we aspire to something big
(no more 2.1.X releases after 2.1.8) we're less likely to see what we
actually want (2.2 out and in use). Strange psychology maybe, but I can
relate to it - I've done it myself :-)
Regards, Upayavira
