Hi castor user, Hi peer committers,
according to recent communication on mailing lists I see a growing
demand to publish a new release. On the other side there are quite some
regression issues open that users observed when they tried to upgrade
from very old release like e.g. 0.9.5 which we normally try to fix at
new releases.
As of today the next release would be 1.1.3 stated as maintenance
release of 1.1. With regard to the important improvements and bugfixes
in current SVN head I would suggest to change this to be a feature
release called 1.2. As usual for feature releases I think we should plan
for milestone releases as follows:
1.2 M1: resolved issues of 1.1.3 to be released asap
1.2 M2: issues of 1.1.3 to be resolved before final (2 weeks after M1)
1.2: only improvements to docs (2 weeks after M2)
1.2.1: issues of 1.1.3 that do not make it into 1.2
1.3: issues currently assigned to 1.2
I'm looking forward the hear your thoughts / opinons?
Regards
Ralf
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
