Jukka Zitting wrote:
how about always suffixing release candidates that are voted on with
-rcN, and after acceptance releasing the same binaries again, this
time without suffixes? their md5 checksums would be identical, so
there should be no confusion as to which rc it is, and the release
would have the proper version.
Good idea, but unfortunately we have the version number embedded
within the packages. It is included for example in the jar manifest
and in the Maven POM found in both in the source and binary packages.
Why not just change the version in the pom.xml to 1.2.0-rc1 before doing the rcX
release? If you use the maven release plugin this means no extra work at all.
This way files like manifest etc should contain the right version number. If
there are files that don't take the version number of the pom.xml, we should
consider adjust the build process.
my 2 cents,
Christoph
