You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@polygene.apache.org by "Paul Merlin (JIRA)" <ji...@apache.org> on 2015/07/21 12:44:04 UTC
[jira] [Commented] (ZEST-100) Document the release process
[ 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)
Re: [jira] [Commented] (ZEST-100) Document the release process
Posted by Paul Merlin <pa...@nosphere.org>.
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.
WDYAT?
/Paul
Re: [jira] [Commented] (ZEST-100) Document the release process
Posted by Paul Merlin <pa...@nosphere.org>.
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
> press@apache.org
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
Re: [jira] [Commented] (ZEST-100) Document the release process
Posted by Niclas Hedhman <ni...@hedhman.org>.
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
press@apache.org
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) <ji...@apache.org> 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