Thanks for your feedback Niclas. I updated the document at https://zest.apache.org/java/develop/releasing-apache.html Applied your feedback, clarified things ...
Niclas Hedhman a écrit : > First, > <quote> > > Prepare the two following files: > > - apache-zest-java-<RELEASE-VERSION>-release-notes.txt > - apache-zest-java-<RELEASE-VERSION>-release-notes.adoc > > We will use them later. > > </quote> > > What does "prepare" mean, and if that is "create" then create where? I reworded this section and hope it's clear enough now. > 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? > Thirdly, > > We should have in there somewhere to coordinate a press release with > [email protected] I added a section about this, almost empty, would you mind adding some there? > But it is very good to have all this documented (so we in future can > automate some of this away). Thanks Sure, a lot could be automated. One step at a time :) /Paul
