accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Newton (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (ACCUMULO-3156) Document full release process
Date Sat, 20 Sep 2014 13:38:34 GMT

    [ https://issues.apache.org/jira/browse/ACCUMULO-3156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14141731#comment-14141731
] 

Eric Newton edited comment on ACCUMULO-3156 at 9/20/14 1:38 PM:
----------------------------------------------------------------

My notes thus far:


Add the next version to JIRA.

A PGP key needs to be made. GnuPGP is one way to do this. More details can be found on the
Apache Guide for New Committers.

Once the key is made, you will need to use gpg-agent or something similar to cache your key
and credentials so that the maven gpg plugin can properly sign all the artifacts.

You will need to add your gpg public key to the keys file:
https://dist.apache.org/repos/dist/release/accumulo


The following was placed in my settings.xml. Do this only if you are on a secure box. If not,
use the instructions from this link: 

https://wiki.apache.org/commons/UsingNexus#Preparations_for_using_Nexus

{noformat}
<server>
  <id>apache.snapshots.https</id>
  <username>apacheId</username>
  <password>apachePassword</password>
</server>
<!-- To publish a release -->
<server>
  <id>apache.releases.https</id>
  <username>apacheId</username>
  <password>apachePassword</password>
</server>
{noformat}

Go to the "Road Map" in JIRA under the Accumulo project and click on "Release Notes" under
the unreleased version in question. Note that this will give you open tickets as well. One
way to do this is to look @ all the open tickets for the version and remove them manually
from the release notes. Depending on the type of release, it's possible now could be a good
time to move the versions of the JIRA tickets to the next unreleased bugfix for the major
version line you are releasing.


Run the following commands to branch and release:

{noformat}
git co -b 1.6.2-SNAPSHOT

[19:44][cjnolet@coreys-mbp:/workspace/accumulo(1.6.2-SNAPSHOT)]$ git push -u origin 1.6.2-SNAPSHOT:1.6.2-SNAPSHOT
Total 0 (delta 0), reused 0 (delta 0)
To http://git-wip-us.apache.org/repos/asf/accumulo.git
 * [new branch]      1.6.2-SNAPSHOT -> 1.6.2-SNAPSHOT
Branch 1.6.2-SNAPSHOT set up to track remote branch 1.6.2-SNAPSHOT from origin.

[19:44][cjnolet@coreys-mbp:/workspace/accumulo(1.6.2-SNAPSHOT)]$ mvn release:prepare 

git co 1.6.1

git co -b 1.6.1-rc1

git push -u origin 1.6.1-rc1:1.6.1-rc1
{noformat}

Fire off a message to the dev list with the following template:

{noformat}

Devs,

Please consider the following candidate for Apache Accumulo 1.6.1

Branch: 1.6.1-rc1
SHA1: 88c5473b3b49d797d3dabebd12fe517e9b248ba2
Staging Repository: https://repository.apache.org/content/repositories/orgapacheaccumulo-1017/

Source tarball: http://repository.apache.org/content/repositories/orgapacheaccumulo-1017/org/apache/accumulo/accumulo/1.6.1/accumulo-1.6.1-src.tar.gz
Binary tarball: http://repository.apache.org/content/repositories/orgapacheaccumulo-1017/org/apache/accumulo/accumulo/1.6.1/accumulo-1.6.1-bin.tar.gz
(Append ".sha1", ".md5" or ".asc" to download the signature/hash for a
given artifact.)

Signing keys available at: https://www.apache.org/dist/accumulo/KEYS

Over 1.6.1, we have 188 issues resolved https://git-wip-us.apache.org/repos/asf?p=accumulo.git;a=blob;f=CHANGES;h=91b9d31e3b9dc53f1a576cc49bbc061919eb0070;hb=1.6.1-rc1

Testing: All unit and functional tests are passing. 

Vote will be open until Thursday, September 25th 12:00AM UTC (9/24 8:00PM ET, 9/24 5:00PM
PT)
{noformat}




was (Author: sonixbp):
My nodes thus far:


Add the next version to JIRA.

A PGP key needs to be made. GnuPGP is one way to do this. More details can be found on the
Apache Guide for New Committers.

Once the key is made, you will need to use gpg-agent or something similar to cache your key
and credentials so that the maven gpg plugin can properly sign all the artifacts.

You will need to add your gpg public key to the keys file:
https://dist.apache.org/repos/dist/release/accumulo


The following was placed in my settings.xml. Do this only if you are on a secure box. If not,
use the instructions from this link: 

https://wiki.apache.org/commons/UsingNexus#Preparations_for_using_Nexus

{noformat}
<server>
  <id>apache.snapshots.https</id>
  <username>apacheId</username>
  <password>apachePassword</password>
</server>
<!-- To publish a release -->
<server>
  <id>apache.releases.https</id>
  <username>apacheId</username>
  <password>apachePassword</password>
</server>
{noformat}

Go to the "Road Map" in JIRA under the Accumulo project and click on "Release Notes" under
the unreleased version in question. Note that this will give you open tickets as well. One
way to do this is to look @ all the open tickets for the version and remove them manually
from the release notes. Depending on the type of release, it's possible now could be a good
time to move the versions of the JIRA tickets to the next unreleased bugfix for the major
version line you are releasing.


Run the following commands to branch and release:

{noformat}
git co -b 1.6.2-SNAPSHOT

[19:44][cjnolet@coreys-mbp:/workspace/accumulo(1.6.2-SNAPSHOT)]$ git push -u origin 1.6.2-SNAPSHOT:1.6.2-SNAPSHOT
Total 0 (delta 0), reused 0 (delta 0)
To http://git-wip-us.apache.org/repos/asf/accumulo.git
 * [new branch]      1.6.2-SNAPSHOT -> 1.6.2-SNAPSHOT
Branch 1.6.2-SNAPSHOT set up to track remote branch 1.6.2-SNAPSHOT from origin.

[19:44][cjnolet@coreys-mbp:/workspace/accumulo(1.6.2-SNAPSHOT)]$ mvn release:prepare 

git co 1.6.1

git co -b 1.6.1-rc1

git push -u origin 1.6.1-rc1:1.6.1-rc1
{noformat}

Fire off a message to the dev list with the following template:

{noformat}

Devs,

Please consider the following candidate for Apache Accumulo 1.6.1

Branch: 1.6.1-rc1
SHA1: 88c5473b3b49d797d3dabebd12fe517e9b248ba2
Staging Repository: https://repository.apache.org/content/repositories/orgapacheaccumulo-1017/

Source tarball: http://repository.apache.org/content/repositories/orgapacheaccumulo-1017/org/apache/accumulo/accumulo/1.6.1/accumulo-1.6.1-src.tar.gz
Binary tarball: http://repository.apache.org/content/repositories/orgapacheaccumulo-1017/org/apache/accumulo/accumulo/1.6.1/accumulo-1.6.1-bin.tar.gz
(Append ".sha1", ".md5" or ".asc" to download the signature/hash for a
given artifact.)

Signing keys available at: https://www.apache.org/dist/accumulo/KEYS

Over 1.6.1, we have 188 issues resolved https://git-wip-us.apache.org/repos/asf?p=accumulo.git;a=blob;f=CHANGES;h=91b9d31e3b9dc53f1a576cc49bbc061919eb0070;hb=1.6.1-rc1

Testing: All unit and functional tests are passing. 

Vote will be open until Thursday, September 25th 12:00AM UTC (9/24 8:00PM ET, 9/24 5:00PM
PT)
{noformat}



> Document full release process
> -----------------------------
>
>                 Key: ACCUMULO-3156
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3156
>             Project: Accumulo
>          Issue Type: Task
>            Reporter: Corey J. Nolet
>            Assignee: Corey J. Nolet
>
> This should apply both to people who are familiar with the release process but want a
quick checklist or people who are new to the release process and have never done it before.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message