Carsten Ziegeler wrote:
>
> Hi Team,
>
> it seems that it is time to think of some release plans.
> Thanks to Giacomo we have the new directory structure in our CVS
> and thanks to all of us we have a working HEAD cvs, so we can
> deprecate the 2.0 branch making the development much easier for
> all of us.
>
> So, these questions need to be answered:
> a) What is the version of the next release?
>
> b) Are there open problems/bugs which must be fixed?
>
> c) Are there outstanding issues which should go into a next release?
>
> d) What is a possible timeframe for the next release?
>
> Any others?
>
> My personal answers to this are:
> a) 2.0.1
+1 if absolutely *no* back incompatible changes are introduced.
2.1 if the above is not true.
> b) At least making Deli optional
+1
> c) - The reintegration of the components moved to Avalon
> - Have more official releases, like final Xalan, final Avalon Framework
> and Excalibur etc.
+1
> d) This is the hard question. If we have no points for b) and c), we could
> do a next release in the next weeks.
+1, end of January?
> So if the vote results in making a release immediately without
> integrating
> further new features, I would propose a beta for the end of this month
> with a feature stop right now!
No, no, no betas or RC, as long as we keep back compatibility we release
and we go. If a bugfix is needed 2.0.2 will fix it.
> I would like to have the points mentioned in c) integrated in a next
> release,
> so perhaps a beta could go out around the end of february.
That's more than a couple of week in my calendar. <puzzled/>
--
Stefano Mazzocchi One must still have chaos in oneself to be
able to give birth to a dancing star.
<[EMAIL PROTECTED]> Friedrich Nietzsche
--------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
