> > So... the question is, should we start implementing our forms > > in Woody, possibly working with misfeatures that haven't yet > > had the kinks shaken out, and knowing that we'll have to migrate > > to CForms later? > > Or should we start using the not-yet-stable Cocoon 2.1.5, > > develop in not-yet-stable CForms, knowing we'll need to upgrade > > Cocoon again when 2.1.5 stable release comes out? > > > > I'm thinking that the former is better, since we won't have > > as much of the headache of working with an unstable framework. > > But I'd welcome your thoughts. > > CForms is not less stable than Woody, I would even say it's the other > way around, because the API is cleaned at the moment - but maybe this > "at the moment" is important. But IMO the headache by upgrading from > 2.1.4 and Woody to 2.1.5 and CForms might be bigger than the usage of > the current CForms. > Furthermore the 2.1.5 seems not to be that far away. We > already agreed > in starting the code freeze after next First Friday and to > release one > week later, on 14th of May.
Thanks for the helpful advice. I was assuming, based on past patterns, that the 2.1.5 stable release would be at least a few (if not several) months away. Lars --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
