Vadim Gritsenko wrote:That wasn't my impression. My understanding was that, while the board discussed this internally, we should carry on 'as normal'. They would offer a clarification when they have one.
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.Yes, agreed. But do we need a 2.1.5?
Yes, I really would love to do it in the order you suggest, butThus, 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.
unfortunately
we can't make a release because of the licensing problems.
If we think we need a release, we should check this.
Personally, I think getting CForms out in its current form is worth a release.
Regards, Upayavira
So, we have a lot of nice code for 2.2 lying around and are not apply to check it in. And who knows how long it will take until we can make a 2.1.5 release, so I want to start right now with 2.2. Of course, if we can solve the licensing issue right now, I'm +5 on this!
Carsten
