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? 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? Thirdly, We should have in there somewhere to coordinate a press release with [email protected] But it is very good to have all this documented (so we in future can automate some of this away). Thanks Niclas On Tue, Jul 21, 2015 at 1:44 PM, Paul Merlin (JIRA) <[email protected]> wrote: > > [ > https://issues.apache.org/jira/browse/ZEST-100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14634929#comment-14634929 > ] > > Paul Merlin commented on ZEST-100: > ---------------------------------- > > Gang, > > I came up with a release guide for Apache Zest: > https://zest.apache.org/java/develop/releasing-apache.html > > Source can be found here: > https://github.com/apache/zest-qi4j/blob/develop/manual/src/docs/tutorials/howto-releasing-apache.txt > > If someone is willing to review it and comment I'd be happy. > > Cheers > > > Document the release process > > ---------------------------- > > > > Key: ZEST-100 > > URL: https://issues.apache.org/jira/browse/ZEST-100 > > Project: Zest > > Issue Type: Sub-task > > Reporter: Paul Merlin > > Assignee: Paul Merlin > > > > Start from https://www.apache.org/dev/release.html and > https://www.apache.org/dev/publishing-maven-artifacts.html > > > > -- > This message was sent by Atlassian JIRA > (v6.3.4#6332) > -- Niclas Hedhman, Software Developer http://zest.apache.org - New Energy for Java
