incubator-blur-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Blur Wiki] Update of "HowToRelease" by AaronMcCurry
Date Sat, 15 Mar 2014 23:28:58 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Blur Wiki" for change notification.

The "HowToRelease" page has been changed by AaronMcCurry:
https://wiki.apache.org/blur/HowToRelease?action=diff&rev1=29&rev2=30

  Ensure that you have setup your ssh keys on people.apache.org, otherwise you'll have to
enter your login password a number of times (best use ssh-agent for this as well). A good
overview of this process can be found [[http://www.thegeekstuff.com/2008/11/3-steps-to-perform-ssh-login-without-password-using-ssh-keygen-ssh-copy-id/|here]]
(ssh-copy-id and ssh-agent in particular)
  
  =  Create a Release Series Branch =
+ 
+ If the release is 0.X.0 release then you will need to create a branch.  However if the release
is a 0.X.Y (or minor release) there should already be a branch for the release series.  For
example to release 0.2.0 a branch of apache-blur-0.2 will need to be created, however if the
release was for 0.2.1 then you will reuse the existing branch and just tag the new release
(this is later in the instructions).
+ 
+ For the first release of a release series:
  
   * Update CHANGES.txt in trunk for the new release.
    * Grab the text-based release notes for this release [[https://issues.apache.org/jira/secure/ConfigureReleaseNote.jspa?projectId=12313721|from
JIRA]]
@@ -32, +36 @@

    * Commit: 
  {{{ 
  git add CHANGES.txt
- git commit -m "Preparing for release X.Y.Z" 
+ git commit -m "Preparing for release X.Y.0-incubating" 
  git push origin master
  }}}
   * Create a branch for the release series: 
@@ -41, +45 @@

  git push origin apache-blur-X.Y
  }}}
  
+ For any release following in the same series:
+ 
+  * Update CHANGES.txt.
+   * Grab the text-based release notes for this release [[https://issues.apache.org/jira/secure/ConfigureReleaseNote.jspa?projectId=12313721|from
JIRA]]
+   * Prepend CHANGES.txt with those release notes, adding the title: Release X.Y.Z - YYYY-MM-DD.
+   * Commit: 
+ {{{ 
+ git checkout apache-blur-X.Y
+ git add CHANGES.txt
+ git commit -m "Preparing for release X.Y.Z-incubating" 
+ git push origin apache-blur-X.Y
+ }}}
+ 
  NOTE: After the release has been voted on and is successful then bump of the version of
master.  (See instruction below)
  
  =  Update the Release Branch =
  
- The version number in the release branch ends in -SNAPSHOT, but we need to remove this for
the release. For example, 0.1.0-SNAPSHOT needs to be changed to 0.1.0 
+ The version number in the release branch ends in -SNAPSHOT, but we need to remove this for
the release. For example, 0.1.0-incubating-SNAPSHOT needs to be changed to 0.1.0-incubating
  
  {{{ 
  for file in $(find . -name pom.xml); do 
- sed -i "" -e "s/0.1.0-SNAPSHOT/0.1.0/" $file; 
+ sed -i "" -e "s/0.1.0-incubating-SNAPSHOT/0.1.0-incubating/" $file; 
  done 
  }}}
  
- You will also need to update the version in these files:
+ You will also need to verify/update the version in these files:
  
   * Update the version in docs/cluster-setup.html 
   * Update the version in docs/data-model.html 
@@ -65, +82 @@

  Run all the unit tests with the following: 
  
  {{{ 
- mvn clean test 
+ mvn clean test -Dhadoop1
  }}}
  
  =  Generate the Release Notes =
@@ -93, +110 @@

  
  Build the artifacts: 
  {{{ 
- mvn install
+ mvn install -Dhadoop1
- mvn site -Ddependency.locations.enabled=false
+ mvn site -Ddependency.locations.enabled=false -Dhadoop1
- mvn site:stage
+ mvn site:stage -Dhadoop1
- mvn package -DskipTests
+ mvn package -DskipTests -Dhadoop1
- }}}
- 
- This is a TODO item.
- 
- Create a maven settings file {{{~/.m2/settings.xml}}} with the following content: 
- 
- {{{ 
- <settings> 
- <servers> 
- <server> 
- <id>apache.snapshots.https</id> 
- <username>APACHE-ID</username> 
- <password>APACHE-PASSWORD</password> 
- </server> 
- <server> 
- <id>apache.staging.https</id> 
- <username>APACHE-ID</username> 
- <password>APACHE-PASSWORD</password> 
- </server> 
- <server> 
- <id>apache.releases.https</id> 
- <username>APACHE-ID</username> 
- <password>APACHE-PASSWORD</password> 
- </server> 
- </servers> 
- </settings> 
- }}} 
+ }}}
- 
- 
- The following command deploys the artifacts, checksums, and signatures (you will need to
enter a GPG passphrase) to the [[https://repository.apache.org/index.html#stagingRepositories|Apache
Staging repo]]. 
- 
- {{{ 
- mvn deploy
- }}}
- 
- If this step fails with an ''Access denied'' error check that you have the required permissions
on [[https://repository.apache.org/index.html|Nexus]]. 
- 
- Login to [[https://repository.apache.org|https://repository.apache.org]] using your Apache
credentials. Click on *Staging* on the left. Then click on *org.apache.blur* in the list of
repositories. In the panel below you should see an open repository that is linked to your
username and IP. Select this repository and click *Close*. This will close the repository
from future deployments and make it available for others to view. 
  
  =  Copy Release Artifacts =
  
@@ -244, +224 @@

  The maven site that is generated
   * {{{docs/site/**}}}
  
- 
- 
  =  Commit and Tag =
  
- Commit changes in the branch and create a release tag: 
+ Commit any changes in the branch and create a release tag: 
  
  {{{ 
- git commit -am "Preparing for release X.Y.Z" 
+ git commit -am "Preparing for release X.Y.Z-incubating" 
- git push origin branch-X.Y:branch-X.Y 
+ git push origin apache-blur-X.Y
- git tag -a release-X.Y.Z -m "Blur X.Y.Z release" 
+ git tag -a release-X.Y.Z-incubating -m "Blur X.Y.Z-incubating release" 
- git push origin release-X.Y.Z 
+ git push origin release-X.Y.Z-incubating
  }}}
  
  =  Run the Vote =
@@ -289, +267 @@

  The release needs 3 +1 votes from the PMC. 
  
  = Bump Version in master =
+ 
+ NOTE: Master branch in Blur is strange state, skip this section for now.
  
   * Bump the version number in trunk (the update-versions script mangles the whitespace in
the root XML element): 
  {{{ 

Mime
View raw message