Re: [CocoonForms] END of code freeze

[Jorg Heymans]

Deprecating before removing seems the best option if you care about the 
installed userbase...  Just keep both of them for one more release so 
people can assess the work involved in migrating.

It's the more "gentle" approach :-)

Jorg

Vadim Gritsenko wrote:
Guido Casper wrote:

Vadim Gritsenko wrote:

But, either way this ends up, I'm -1 on keeping both blocks in the 
release. This means the block must be removed before end of month.


Vadim, I (kindly :-) ask you to revert your -1. I have a project using 
Woody running on 2.1.4 (not CVS head) and that would force me to 
upgrade to 2.1.5 AND CForms at the same time while I would prefer 
doing it seperately.

+1 to remove it in 2.1.6


Ummm... If I'm alone in this, I can change to -0 :-)
WDOT?
Vadim