Stefan Seelmann wrote:
Hi Users and Dev,
Hi Stefan,
<snip/>
In the last vote about the final 1.3.0 release we discussed whether we
could just declare the 1.3.0-RC2 packages as 1.3.0 or if we need to
create new packages (with no code change, just new labels).
I think we could avoid such discussions if we switch back to the old
release model: Once we have enough new features we relaese a new x.y.0
version, Then if a major bug is reported we release a x.y.1 and x.y.2,
but only if necessary.
Seems enough to me. Studio team has proved that they were able to
release fast.
Pierre-Arnaud and I collected some arguments, please feel free to add
you own.
Pro RCs:
- helps to not release a really buggy final version
- better suits to common Open Source release model
Contra RCs:
- has less impact on the audience
- increases the number of release (which is time consuming)
- the feedback we've had from the RCs is very low, we've not received a
lot of jiras
- increases the number of uploads, downloads and space required on
apache and mirror servers and on the maven repository
Add the fact that with -RC tags, you can't keep the alphabetic order in
updates, which is painfull (ie, 1.0 will appears to be older than
1.0-RC3, for instance)
--
--
cordialement, regards,
Emmanuel Lécharny
www.iktek.com
directory.apache.org
