[EMAIL PROTECTED] schrieb:
On 4/21/08, Richard Frovarp <[EMAIL PROTECTED]> wrote:
We should probably come up with a new recommended version of Java for Lenya
2.0. 1.4.2 is end of standard life on October 30, 2008. <snip/>
Richard
We should probably upgrade the minimum Java version to 1.5 for Lenya
2.1 because Java 1.4 is near EOL.
+1
We should think about upgrading
dependent libraries immediately after creating the Lenya-2.0 branch
when Trunk becomes Lenya-2.1.
+1
We should coordinate to convert all Collections to Generics.
+1 for internal use. In 2.1, we shouldn't change the API. In 3.0 we can
also change the API to use Generics.
After 2.1 is released, we should think about upgrading the minimum
Java version to 1.6 for Lenya 2.2 or a later release.
(no idea yet)
Thoughts:
1. A version of Lenya is designed for each version of Java. Anybody
requiring a specific version of Java for a CMS will not discard Lenya
because we do not have a gold version available.
I don't quite understand this - does this mean we should provide
"flavors" of each release which are tested with a specific Java version,
or does it mean that a release is designed for a specific Java version?
2. Small steps at each minor release. Tthe conversion to Generics may
take time.
+1
3. SOP should upgrade dependencies when and only when creating
branches. (I made a mistake upgrading XalanJ while fixing a bug and
losing compatibility with Cocoon-2.1.11.)
I'm not quite sure about this. What if there's a bug in a dependency? We
can't create a branch everytime this happens ...
-- Andreas
--
Andreas Hartmann, CTO
BeCompany GmbH
http://www.becompany.ch
Tel.: +41 (0) 43 818 57 01
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
