Werner,

the idea behind the milestones was to be able to ship one asap. I think, for those waiting on a release a milestone maybe more acceptable to be included in their application then a snapshot. In addition it will allow us to focus on that regression issues where users moan most for the final release. Also a milestone shows that we have a feature freeze.

Havind said that I also recognized that milestones have not be tested intesive in the past and that I am not stick to publish one. I can also live without them.

Regards
Ralf

Werner Guttmann schrieb:
Ralf,

please see inline ....

Werner

Ralf Joachim wrote:
Hi castor user, Hi peer committers,

according to recent communication on mailing lists I see a growing demand to publish a new release.
I am about to get the very same feeling(s).

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.
Same here. It looks like with 1.1 and 1.1.2 we finally managed to convince quite some users to switch away from the pre 1.0 releases. And yes, I agree that we should try to fix those regression issues before trying to ship the next release. But as always, this will impact users who are already waiting for a fix that has been applied.

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.
+1.

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)
Not sure. In the past, milestone releases have not been used extensively for testing. To introduce a faster turn-around, I would favour skipping those. Not sure, though.

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




---------------------------------------------------------------------
To unsubscribe from this list please visit:

   http://xircles.codehaus.org/manage_email

--

Syscon Ingenieurbüro für Meß- und Datentechnik GmbH
Ralf Joachim
Raiffeisenstraße 11
72127 Kusterdingen
Germany

Tel.   +49 7071 3690 52
Mobil: +49 173 9630135
Fax    +49 7071 3690 98

Internet: www.syscon.eu
E-Mail: [EMAIL PROTECTED]

Sitz der Gesellschaft: D-72127 Kusterdingen
Registereintrag: Amtsgericht Stuttgart, HRB 382295
Geschäftsleitung: Jens Joachim, Ralf Joachim

---------------------------------------------------------------------
To unsubscribe from this list please visit:

   http://xircles.codehaus.org/manage_email

Reply via email to