I'm with Geoff, same votes for me, also adding mention that Flow is to be considered beta.
-Bertrand


Le Samedi, 14 juin 2003, à 13:16 Europe/Zurich, Geoff Howard a écrit :

[ -.5 ] Release Cocoon 2.1 /immediately/. Carsten suggested the 24th of

Agree with Upayavira on the need and use of a release marked "beta".



[ +1 ] Release Cocoon 2.1 beta 1 /immediately/ (24th of June). This means
more or less ignoring the FOM too. It's for a stabilization phase.


[ -.5 ] Release further milestones while implementing the FOM. Cocoon 2.1
will be released subsequently.



I feel like so much has happened in the flow during this final "milestone"
phase that the API might become stable but the rest will be untested. So
what to do about flow? Make clear that it is a "beta" of flow that will
have to solidify as 2.1 matures.



With Cocoon 2.0.5 it's simpler. No big things have to be done delaying a
release. IMO it's only about the time to release a further minor
release, 2.0.4 is almost exactly half a year old.


[ +1 ] Release Cocoon 2.0.5 as soon as possible.


Reply via email to