As I understood Carsten's reasoning, 2.1.5 cannot be released because it introduces an incompatibility with 2.1.4.
And my opinion goes in different direction. I'll repeat: new laws should not be applied retroactively. And based on this, I proposed another plan of action.
Therefore he was recommending NOT
having a 2.1.5 but going to 2.2 instead. 2.1 would basically be dead.
And I'm recommending to make a 2.1.5 before going to 2.2.
Vadim
Ralph
-----Original Message-----
From: Vadim Gritsenko [mailto:[EMAIL PROTECTED] Sent: Friday, April 23, 2004 9:27 AM
To: [EMAIL PROTECTED]
Subject: Re: [Vote] Repository Usage and Versioning
I don't think new policy which is being voted in should be applied retroactively. Meaning, I'd suggest this policy to be in effect starting with Cocoon 2.1.5.
Thus, plan of action would be in this case: * Let Cocoon 2.1.5 out. * Move to Subcersion. * Start Cocoon 2.2. * Remove deprecated classes in 2.2 which Carsten mentioned recently.
Vadim
