polygene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul Merlin <p...@nosphere.org>
Subject Re: [jira] [Commented] (ZEST-100) Document the release process
Date Wed, 22 Jul 2015 09:44:07 GMT
Paul Merlin a écrit :
>> Second,
>> an RC# will actually not be a Maven pushed set of artifacts with that RC#
>> in version, only used in the tarball. And the Maven will be overridden in
>> staging if the vote fails and a new release is cut?
> The only leftovers of a failed release-candidate are:
> 1. emails
> 2. unsigned <RELEASE-VERSION>-RC# git tag
> 3. src & bin distributions svn history at
> https://dist.apache.org/repos/dist/dev/zest/
> Maven RC artifacts are dropped, the next RC will use a new staging
> repository, see "VOTE fails/Drop RC artifacts and distributions".
> Maybe 3. has an issue as release distributions files do not exhibit the
> RC# in their name?
We could rename them with the -RC# before upload to svn/dist/~/dev and
then remove the -RC# from their name before upload to svn/dist/~/release
if the vote pass. That way, they exhibit -RC# in their names when in
svn/dist/~/dev and its history ; they exhibit the proper release version
when in svn/dist/~/release.

Convenience maven artifacts never exhibit the -RC# version as only
successful releases are promoted.

Note that as our build system generates code with versionning
information in constants, we cannot build using -RC# in version and
later promote the same bits. Versionning information would then contains
-RC# but shouldn't.



  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message