incubator-bval-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From conflue...@apache.org
Subject [CONF] Apache Bean Validation > Release Process
Date Tue, 25 May 2010 20:14:00 GMT
Space: Apache Bean Validation (http://cwiki.apache.org/confluence/display/BeanValidation)
Page: Release Process (http://cwiki.apache.org/confluence/display/BeanValidation/Release+Process)

Change Comment:
---------------------------------------------------------------------
split onto its own page

Edited by Donald Woods:
---------------------------------------------------------------------
We'll be using the Apache Nexus repository (repository.apache.org) for releasing SNAPSHOT
and release artifacts.  More details on releasing artifacts and using Nexus can be found on
the Maven website at - [http://maven.apache.org/developers/release/apache-release.html]


# Environment setup for releasing artifacts (same for SNAPSHOTs and releases) -
## Increase the default Java heap available to Maven (required for Java SE 6)
{code:none}
export MAVEN_OPTS="-Xmx1024m -XX:MaxPermSize=256m"
{code}
## Use the latest Sun 1.6.0 JDK
## Use Maven 2.2.1 or later (2.2.1 is required for release signing fixes)
## Make sure the [Release Setup] steps have been performed.
# Prepare the source for release: 
## Cleanup JIRA so the Fix Version in issues resolved since the last release includes this
release version correctly.  Also, transition any Resolved issues to the Closed state.
## Update the text files in a working copy of the project root -
### Update the CHANGES.txt based on the Text release reports from JIRA.
### Review and update README.txt if needed.
### Commit any changes back to svn -
{code:none}
$ svn commit -m "updating files for release"
{code}
## Stage any Roadmap or Release landing pages on the wiki.
## Use "mvn rat:check" to verify the source has the required headers before trying to release.
## Perform a full build and TCK runs before trying to release.
# For new major releases (like 1.0.0 to 1.1.0)
## Create a sub-branch from which to make the release. Releasing from a branch will allow
any cosmetic changes that need to be made for the release to be approved to be done without
preventing other more disruptive advances in the trunk from potentially causing problems with
the release. It also provides a future maintenance branch (like 1.0.x.)  A branch can be made
by running: \\
{code:none}
$ mvn release:branch -DbranchName=1.0.x
{code}
# Checkout a clean copy of the trunk/branch to release using command line svn.
## Do not use Eclipse to do the checkout.  The extra dot (.) files created by Eclipse throws
off the rat:check processing. \\
{code:none}
$ svn checkout https://svn.apache.org/repos/asf/incubator/bval/trunk/ 0.1-rc1/
{code}
# Do a dry run of the release:prepare step.
## The dry run will not commit any changes back to SVN and gives you the opportunity to verify
that the release process will complete as expected. You will be prompted for the following
information :
### Release version - take the default - (default 0.1-incubating) 
### SCM release tag - *DO NOT TAKE THE DEFAULT - (default bval-0.1-incubating): : 0.1-incubating
### New development version - take the default - (default 0.2-incubating-SNAPSHOT) 
### _optional_ if you have not specified a GPG passphrase in settings.xml you will be prompted
for it. 
{code:none}
$ mvn -Papache-release release:prepare -DdryRun=true
<snip>
[INFO] Working directory: /Users/drwoods/bval/0.1-rc1
[INFO] Checking dependencies and plugins for snapshots ...
What is the release version for "Apache Bean Validation :: bval-parent (Parent POM)"? (org.apache.bval:bval-parent)
0.1-incubating: : 
What is SCM release tag or label for "Apache Bean Validation :: bval-parent (Parent POM)"?
(org.apache.bval:bval-parent) bval-parent-0.1-incubating: : 0.1-incubating
What is the new development version for "Apache Bean Validation :: bval-parent (Parent POM)"?
(org.apache.bval:bval-parent) 0.2-incubating-SNAPSHOT: : 
[INFO] Transforming 'Apache Bean Validation :: bval-parent (Parent POM)'...
<snip>
{code}
# Verify that the release process completed as expected
## The release plugin will create pom.xml.tag files which contain the changes that would have
been committed to SVN. The only differences between pom.xml.tag and it's corresponding pom.xml
file should be the version number.
## If other formatting changes have been made you should review the changes and then commit
them -
{code:none}
$ svn commit -m "fixing formatting for release"
{code}
## Assuming the .tag files look OK you may proceed and do any other validation you feel necessary.
The following list may be helpful 
### Check release.properties and make sure that the scm properties have the right version.
Sometimes the scm location can be the previous version not the next version.
### verify signatures [#Verifying release signatures]
### if you have access to the TCK, run it [JSR303 TCK]
## Once any failures or required updates have been committed to svn, rollback the release
prepare files -
{code:none}
$ mvn -Papache-release release:rollback
{code}
# Prepare the release
## Run the "release:prepare" step for real this time.  You'll be prompted for the same version
information and optionally your GPG passphrase again.
{note}Different arguments and steps are required as there are problems with the maven-jar-plugin
and maven-release-plugin when using the test-jar goal.  See [http://jira.codehaus.org/browse/MJAR-68]
 and [http://jira.codehaus.org/browse/MRELEASE-285].
{note}
{code:none}
$ mvn -DskipTests=true -Papache-release release:prepare -DpreparationGoals="clean install"
  [ERROR] BUILD ERROR
$ mvn clean install -Dtest=false -DfailIfNoTests=false -Dmaven.test.execute=false
  [INFO] BUILD SUCCESSFUL
$ mvn -DskipTests=true -Papache-release release:prepare -DpreparationGoals="clean install"
  [INFO] BUILD SUCCESSFUL
{code}
# Backup (zip or tar) your local release candidate directory incase you need to rollback the
release after the next step is performed.
{code:none}
cd ..
tar -czf 0.1-rc1.tar.gz 0.1-rc1/
cd 0.1-rc1
{code}
# Perform the release
## This step will create a maven staging repository and site for use in testing and voting.
You will be prompted for your repository.apache.org and people.apache.org password several
times if you have not added server profiles to your settings.xml.  See [Release Setup] for
more information. 
{code:none}
$ mvn -Papache-release release:perform -Duser.name=<your_apache_uid>
{code} 
{note} If your local OS userid doesn't match your Apache userid, then you'll have to also
override the value provided by the OS to Maven for the site-deploy step to work.  This is
known to work for Linux, but not for Mac and unknown for Windows.
{note}
## The maven-release-plugin is configured with goals "deploy site site:deploy" and will deploy
the site files to a staging-site directory on people.apache.org.
# Verify the release artifacts
## Verify the HTML links in staging-site/index.html are correct
## Verify the staged artifacts in the nexus repo
### https://repository.apache.org/index.html
### Enterprise --> Staging
### Staging tab --> Name column --> org.apache.bval
### Navigate through the artifact tree and make sure that all javadoc, sources, tests, jars,
... have .asc (GPG signature) and .md5 files.  See [http://people.apache.org/~henkp/repo/faq.html]
and [http://www.apache.org/dev/release-signing.html#openpgp-ascii-detach-sig]
## Close the nexus staging repo
### https://repository.apache.org/index.html
### Enterprise --> Staging
### Staging tab --> Name column --> org.apache.bval
### Right click on the open staging repo (org.apache.bval-XXX) and select Close.
# Put the release candidate up for a vote
## Send an email to bval-dev@incubator.apache.org requesting a vote. [Vote email example|http://markmail.org/message/siwhrukuyu64cncg]
## Example -
{code:none}

{code}
## A -1 vote does not necessarily mean that the vote must be redone however it is usually
a good idea to rollback the release if a -1 vote is received. See - [#Recovering from a vetoed
release]
## After the vote has been open for at least 72 hours, has at least three +1 PMC votes and
no -1 votes, then post the results to the vote thread by -
### replying to the initial email and prepend to the original subject -
{code:none}[RESULTS]{code}
### Include a list of everyone who voted +1, 0 or -1.
# Put the release candidate up for an Incubator PMC vote
## TBD...
## After the vote has been open for at least 72 hours, has at least three +1 PMC votes and
no -1 votes, then post the results to the vote thread by -
### replying to the initial email and prepend to the original subject -
{code:none}[RESULTS]{code}
### Include a list of everyone who voted +1, 0 or -1.
# Finalizing a release
## Promote the staged nexus artifacts -
### https://repository.apache.org/index.html
### Enterprise --> Staging
### Staging tab --> Name column --> org.apache.bval
### Right click on the closed staging repo (org.apache.bval-XXX) and select Promote.
## Copy the staged site over to our website area
### TBD....
{code:none}
$ ssh ${user.name}@people.apache.org 
$ cd ~/public_html/bval/${project.version}/staging-site
{code}
## Copy the distribution artifacts over to the distribution area
### TBD....
## Update the [JIRA versions | https://issues.apache.org/jira/secure/project/ManageVersions.jspa?pid=12311080]
page to mark the version as "released", and set the date to the date that the release was
approved. You may also need to make a new release entry for the next release.
# Announcing the release
## After the mirrors have had time to update (24 hours to be on the safe side) update the
wiki with pointers to the new release
## Make a [news announcement|http://cwiki.apache.org/confluence/pages/createblogpost.action?spaceKey=BeanValidation]
on the BeanValidation wiki.
## Make an announcement about the release on the [mailto:bval-users@incubator.apache.org]
list (and, for major releases, on the [mailto:announce@apache.org] list as per [the Apache
Announcement Mailing Lists page|http://www.apache.org/foundation/mailinglists.html#foundation-announce])


h3. Recovering from a vetoed release
TBD...

h3. Verifying release signatures

On unix platforms the following command can be executed -
{code:none}
for file in `find . -type f -iname '*.asc'`
do
    gpg --verify ${file} 
done
{code}

You'll need to look at the output to ensure it contains only good signatures -
{code:none}
gpg: Good signature from ...
gpg: Signature made ...
{code}


Change your notification preferences: http://cwiki.apache.org/confluence/users/viewnotifications.action
   

Mime
View raw message