You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@bval.apache.org by bu...@apache.org on 2012/03/10 23:51:11 UTC
svn commit: r808152 [6/7] - in /websites/staging/bval/trunk/content: ./
board-reports/ coding/ images/ resources/
Added: websites/staging/bval/trunk/content/release-management.html
==============================================================================
--- websites/staging/bval/trunk/content/release-management.html (added)
+++ websites/staging/bval/trunk/content/release-management.html Sat Mar 10 22:51:09 2012
@@ -0,0 +1,225 @@
+
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<!--
+Licensed to the Apache Software Foundation (ASF) under one
+or more contributor license agreements. See the NOTICE file
+distributed with this work for additional information
+regarding copyright ownership. The ASF licenses this file
+to you under the Apache License, Version 2.0 (the
+"License"); you may not use this file except in compliance
+with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing,
+software distributed under the License is distributed on an
+"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+KIND, either express or implied. See the License for the
+specific language governing permissions and limitations
+under the License.
+-->
+<html>
+<head>
+ <META http-equiv="Content-Type" content="text/html;charset=UTF-8" />
+ <link type="text/css" rel="stylesheet" href="/resources/site.css";></link>
+ <link type="text/css" rel="stylesheet" href="/resources/code.css";></link>
+ <script src="/resources/space.js"; type="text/javascript"></script>
+ <link rel="SHORTCUT ICON" href="/images/favicon.ico">
+ <LINK rel="schema.DC" href="http://purl.org/DC/elements/1.0/">
+ <META name="Description" content="Apache BVal -- Release Management" />
+ <META name="Keywords" content="Apache Bean Validation JSR-303 JavaEE6 " />
+ <META name="Owner" content="bval-dev@incubator.apache.org" />
+ <META name="Robots" content="index, follow" />
+ <META name="Security" content="Public" />
+ <META name="Source" content="wiki template" />
+ <META name="DC.Date" scheme="iso8601" content="2010-05-21" />
+ <META name="DC.Language" scheme="rfc1766" content="en" />
+ <META name="DC.Rights" content="Copyright © 2010, The Apache Software Foundation" />
+ <META http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))'/>
+ <title>
+ Apache BVal
+ </title>
+</head>
+<body>
+
+<table width="100%" cellpadding="0" cellspacing="0">
+ <tr width="100%">
+ <td id="cell-0-0" colspan="2"> </td>
+ <td id="cell-0-1"> </td>
+ <td id="cell-0-2" colspan="2"> </td>
+ </tr>
+ <tr width="100%">
+ <td id="cell-1-0"> </td>
+ <td id="cell-1-1"> </td>
+ <td id="cell-1-2">
+ <div style="padding: 5px;">
+ <div id="banner">
+ <!-- Banner -->
+<p><a name="Banner-Overview"></a></p>
+<table border="0" cellpadding="0" cellspacing="0" width="100%">
+ <tr>
+ <td align="left" nowrap="">
+ <a href="http://incubator.apache.org/bval/" title="Apache BVal">
+ <img border="0" src="/images/check3_71x75.png">
+ </a>
+ </td>
+ <td align="left" class="topbardiv" nowrap="">
+ <a href="/" title="Apache BVal">
+ <img border="0" src="/images/bval_logo.png">
+ </a>
+ </td>
+ <td align="right" nowrap="">
+ <a href="http://www.apache.org/" title="The Apache Software Foundation">
+ <img border="0" src="/images/feather-small.gif">
+ </a>
+ </td>
+ </tr>
+</table>
+ <!-- Banner -->
+ </div>
+ </div>
+ <!--
+ <div id="top-menu">
+ <table border="0" cellpadding="1" cellspacing="0" width="100%">
+ <tr>
+ <td>
+ <div align="left">
+ <a href="/">Home</a>
+ </div>
+ </td>
+ <td>
+ <div align="right">
+$content
+ </div>
+ </td>
+ </tr>
+ </table>
+ </div>
+ -->
+ </td>
+ <td id="cell-1-3"> </td>
+ <td id="cell-1-4"> </td>
+ </tr>
+ <tr width="100%">
+ <td id="cell-2-0" colspan="2"> </td>
+ <td id="cell-2-1">
+ <table>
+ <tr height="100%" valign="top">
+ <td height="100%">
+ <div id="wrapper-menu-page-right">
+ <div id="wrapper-menu-page-top">
+ <div id="wrapper-menu-page-bottom">
+ <div id="menu-page">
+ <!-- NavigationBar -->
+<p><a name="Navigation-Overview"></a></p>
+<h3 id="overview">Overview</h3>
+<ul>
+<li><a href="/board-reports/index.html">Board Reports</a></li>
+<li><a href="http://www.apache.org/licenses/LICENSE-2.0.html">License</a></li>
+<li><a href="/privacy-policy.html">Privacy Policy</a></li>
+</ul>
+<p><a name="Navigation-Community"></a></p>
+<h3 id="community">Community</h3>
+<ul>
+<li><a href="/downloads.html">Downloads</a></li>
+<li><a href="/documentation.html">Documentation</a></li>
+<li><a href="/samples.html">Samples</a></li>
+<li><a href="/roadmap.html">Roadmap</a></li>
+<li><a href="/found-a-bug.html">Found a Bug</a></li>
+<li><a href="/getting-involved.html">Getting Involved</a></li>
+<li><a href="/people.html">People</a></li>
+<li><a href="/mailing-lists.html">Mailing Lists</a></li>
+</ul>
+<p><a name="Navigation-Development"></a></p>
+<h3 id="development">Development</h3>
+<ul>
+<li><a href="https://svn.apache.org/repos/asf/bval/trunk">Source Code</a></li>
+<li><a href="https://issues.apache.org/jira/browse/BVAL">Issue Tracker</a></li>
+<li><a href="/building.html">Building</a></li>
+<li><a href="/coding-standards.html">Coding Standards</a></li>
+<li><a href="/jsr303-tck.html">JSR303 TCK</a></li>
+<li><a href="/release-management.html">Release Management</a></li>
+<li><a href="/automated-builds.html">Automated Builds</a></li>
+</ul>
+<p><a name="Navigation-Sponsorship"></a></p>
+<h3 id="sponsorship">Sponsorship</h3>
+<ul>
+<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsoring Apache</a></li>
+</ul>
+<p><a name="Navigation-Search"></a></p>
+<h3 id="search">Search</h3>
+<p><DIV style="padding: 5px 5px 0px 25px;">
+<FORM action="http://www.google.com/search" method="get" style="font-size:
+10px;">
+ <INPUT name="ie" type="hidden" value="UTF-8"></INPUT>
+ <INPUT name="oe" type="hidden" value="UTF-8"></INPUT>
+ <INPUT maxlength="255" name="q" size="15" type="text" value=""></INPUT>
+ <INPUT name="btnG" type="submit" value="Google Search"></INPUT>
+ <INPUT name="domains" type="hidden" value="bval.apache.org"></INPUT>
+ <INPUT name="sitesearch" type="hidden" value="bval.apache.org"></INPUT>
+</FORM>
+</DIV></p>
+ <!-- NavigationBar -->
+ </div>
+ </div>
+ </div>
+ </div>
+ </td>
+ <td height="100%">
+ <!-- Content -->
+ <div id="BValContent_Release Management" class="wiki-content"><p>We'll be using the <a href="http://repository.apache.org">Apache Nexus repository</a> for
+releasing <code>SNAPSHOT</code> and release artifacts, which uses the same LDAP groups
+as SVN to control who can publish artifacts using <code>groupId=org.apache.bval</code>.</p>
+<p>To familiarize yourself with the notions and requirements for releasing
+artifacts, please check out the
+<a href="http://www.apache.org/dev/release.html">Apache Release FAQ</a>.</p>
+<p>As BVal is a graduated Incubator project, the
+<a href="http://incubator.apache.org/guides/releasemanagement.html">Incubator Release Guidelines</a>
+may be of interest.</p>
+<p><a name="ReleaseManagement-ApacheBValReleaseGuidelines"></a></p>
+<h3 id="apache-bval-release-guidelines">Apache BVal Release Guidelines</h3>
+<ul>
+<li><a href="/release-setup.html">Release Setup</a></li>
+<li><a href="/release-process.html">Release Process</a></li>
+</ul></div>
+ <!-- Content -->
+ </td>
+ </tr>
+ </table>
+ </td>
+ <td id="cell-2-2" colspan="2"> </td>
+ </tr>
+ <tr width="100%">
+ <td id="cell-3-0"> </td>
+ <td id="cell-3-1"> </td>
+ <td id="cell-3-2">
+ <div id="footer">
+ <!-- Footer -->
+ <div id="site-footer">
+ </div>
+ <!-- Footer -->
+ </div>
+ </td>
+ <td id="cell-3-3"> </td>
+ <td id="cell-3-4"> </td>
+ </tr>
+ <tr width="100%">
+ <td id="cell-4-0" colspan="2"> </td>
+ <td id="cell-4-1">
+ <div id="footer-legal">
+Copyright (C) 2010-2012 The Apache Software Foundation. Licensed under <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License 2.0</a>.<br />
+Apache and the Apache feather logo are trademarks of The Apache Software Foundation.<br />
+Other names may be trademarks of their respective owners.
+ </div>
+ </td>
+ <td id="cell-4-2" colspan="2"> </td>
+ </tr>
+ <tr width="100%">
+ <td id="cell-4-0" colspan="2"> </td>
+ <td id="cell-4-1"> </td>
+ <td id="cell-4-2" colspan="2"> </td>
+ </tr>
+</table>
+</body>
+</html>
Added: websites/staging/bval/trunk/content/release-process.cwiki
==============================================================================
--- websites/staging/bval/trunk/content/release-process.cwiki (added)
+++ websites/staging/bval/trunk/content/release-process.cwiki Sat Mar 10 22:51:09 2012
@@ -0,0 +1,262 @@
+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]
+
+h3. Release Steps
+
+# 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 deploy the SNAPSHOT artifacts
+{code:none}
+$ mvn clean deploy -Papache-release
+{code}
+## Run the [JSR303 TCK] to verify the latest code passes.
+## Inspect the files in your local target directories to ensure:
+### All jars and zips include: LICENSE, NOTICE, DISCLAIMER files
+### The NOTICE files cover all third-party included files (like XSD schemas)
+### The LICENSE files include any third-party licenses (none at this time)
+### All jars/zips/poms have .asc (PGP signature) and md5 files
+# 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/bval/trunk/ 1.0-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 1.0)
+### SCM release tag - *DO NOT TAKE THE DEFAULT - (default bval-1.0): : 1.0
+### New development version - take the default - (default 1.0.1-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/1.0-rc1
+[INFO] Checking dependencies and plugins for snapshots ...
+What is the release version for "Apache BVal :: bval-parent (Parent POM)"? (org.apache.bval:bval-parent) 1.0: :
+What is SCM release tag or label for "Apache BVal :: bval-parent (Parent POM)"? (org.apache.bval:bval-parent) bval-parent-1.0: : 1.0
+What is the new development version for "Apache BVal :: bval-parent (Parent POM)"? (org.apache.bval:bval-parent) 1.0.1-SNAPSHOT: :
+[INFO] Transforming 'Apache BVal :: bval-parent (Parent POM)'...
+<snip>
+{code}
+{note}
+If you cancel a release:prepare before it updates the pom.xml versions, then use the *release:clean* goal to just remove the extra files that were created.
+{note}
+# 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 release:prepare -Papache-release -DskipTests=true -DpreparationGoals="clean install"
+{code}
+# Backup (zip or tar) your local release candidate directory in case you need to rollback the release after the next step is performed.
+{code:none}
+cd ..
+tar -czf 1.0-rc1.tar.gz 1.0-rc1/
+cd 1.0-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 release:perform -Papache-release -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
+## Create a VOTE email thread on bval-dev@ to record votes as replies, like -
+{code:none}
+To: bval-dev@
+Subject: [VOTE] Apache BVal 1.0 Release Candidate
+
+I've created a 1.0 release candidate, with the following artifacts up for a vote:
+
+SVN source tag (r950702):
+https://svn.apache.org/repos/asf/bval/tags/1.0/
+
+Maven staging repo:
+https://repository.apache.org/content/repositories/orgapachebval-020/
+
+Source release:
+https://repository.apache.org/content/repositories/orgapachebval-020/org/apache/bval/bval-parent/1.0/bval-parent-1.0-source-release.zip
+
+Javadoc staging site:
+http://people.apache.org/~mbenson/bval/1.0/staging-site/apidocs/
+
+PGP release keys (signed using D018E6B1):
+https://svn.apache.org/repos/asf/bval/KEYS
+
+
+Vote will be open for 72 hours.
+
+[ ] +1 approve
+[ ] +0 no opinion
+[ ] -1 disapprove (and reason why)
+
+{code}
+## Create a DISCUSS email thread on bval-dev@ for any vote questions, like -
+{code:none}
+To: bval-dev@
+Subject: [DISCUSS] Apache BVal 1.0 Release Candidate
+
+Discussion thread for vote on 1.0 release candidate, with SVN source tag (r999999).
+
+For more information on the release process, checkout -
+http://www.apache.org/dev/release.html
+
+Some of the things to check before voting are:
+- does "mvn apache-rat:check" pass on the source
+- can you build the contents of source-release.zip and svn tag
+- do all of the staged jars/zips contain the required LICENSE, NOTICE
+and DISCLAIMER files
+- are all of the staged jars signed and the signature verifiable
+- is the signing key in the project's KEYS file and on a public server
+- does the release pass the TCK
+
+{code}
+## Perform a review of the release and cast your vote. See the following for more details on Apache releases -
+### [http://www.apache.org/dev/release.html]
+## 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 -
+### reply to the initial email and prepend to the original subject -
+{code:none}[RESULT]{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
+{code:none}
+$ ssh ${user.name}@people.apache.org
+$ mkdir /www/bval.apache.org/${project.version}
+$ cp -R ~/public_html/bval/${project.version}/staging-site/* /www/bval.apache.org/${project.version}
+# Make sure all the copied files have g+rw set and only o+r set
+$ cd /www/bval.apache.org
+$ find . -user ${user.name} -type f | xargs chmod 664
+$ find . -user ${user.name} -type d | xargs chmod 775
+{code}
+## Update the *Documentation* wiki page to point to the new apidocs
+{code:none}
+http://bval.apache.org/${project.version}/apidocs/
+{code}
+## Copy the distribution artifacts over to the distribution area
+{code:none}
+$ ssh ${user.name}@people.apache.org
+$ mkdir /www/www.apache.org/dist/bval/${project.version}
+$ cd /www/www.apache.org/dist/bval/${project.version}
+$ wget https://repository.apache.org/content/repositories/releases/org/apache/bval/bval-parent/${project.version}/bval-parent-${project.version}-source-release.zip
+$ wget https://repository.apache.org/content/repositories/releases/org/apache/bval/bval-parent/${project.version}/bval-parent-${project.version}-source-release.zip.asc
+$ wget https://repository.apache.org/content/repositories/releases/org/apache/bval/bval-parent/${project.version}/bval-parent-${project.version}-source-release.zip.md5
+$ wget https://repository.apache.org/content/repositories/releases/org/apache/bval/bval-parent/${project.version}/bval-parent-${project.version}-source-release.zip.sha1
+# Make sure all the copied files have g+rw set and only o+r set
+$ find . -user ${user.name} -type f | xargs chmod 664
+$ find . -user ${user.name} -type d | xargs chmod 775
+# Note: All of the artifacts are in the maven repos, but we may create an assembly to publish in future releases
+{code}
+## Update the *Downloads* wiki page to point to the new release artifacts
+{code:none}
+http://www.apache.org/dyn/closer.cgi/bval/${project.version}/
+http://repo1.maven.org/maven2/org/apache/bval/${artifactId}/${project.version}/
+{code}
+## 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 BVal wiki.
+## Make an announcement about the release on the [mailto:users@bval.apache.org], [mailto:dev@bval.apache.org], and [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
+# Reply to the initial vote email and prepend to the original subject -
+{code:none}[CANCELED]{code}
+# Rollback the version upgrades in trunk by either -
+## Restore the 0.1-rc1.tar.gz and run
+{code:none}
+$ mvn -Papache-release release:rollback
+{code}
+## Manually revert the versions in trunk to the prior version and commit
+# Delete the svn tag created by the release:perform step -
+{code:none}
+$ svn del https://svn.apache.org/repos/asf/bval/tags/1.0 -m "deleting tag from rolled back release"
+{code}
+# Drop the nexus staging repo
+## 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 Drop.
+# Remote the staged site
+{code:none}
+$ ssh ${user.name}@people.apache.org
+$ cd ~/public_html/bval
+$ rm -fr ${project.version}
+{code}
+# Make the required updates that caused the vote to be canceled
+# Spin another release candidate!
+
+\\
+
+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}
+
+\\
Added: websites/staging/bval/trunk/content/release-process.html
==============================================================================
--- websites/staging/bval/trunk/content/release-process.html (added)
+++ websites/staging/bval/trunk/content/release-process.html Sat Mar 10 22:51:09 2012
@@ -0,0 +1,654 @@
+
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<!--
+Licensed to the Apache Software Foundation (ASF) under one
+or more contributor license agreements. See the NOTICE file
+distributed with this work for additional information
+regarding copyright ownership. The ASF licenses this file
+to you under the Apache License, Version 2.0 (the
+"License"); you may not use this file except in compliance
+with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing,
+software distributed under the License is distributed on an
+"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+KIND, either express or implied. See the License for the
+specific language governing permissions and limitations
+under the License.
+-->
+<html>
+<head>
+ <META http-equiv="Content-Type" content="text/html;charset=UTF-8" />
+ <link type="text/css" rel="stylesheet" href="/resources/site.css";></link>
+ <link type="text/css" rel="stylesheet" href="/resources/code.css";></link>
+ <script src="/resources/space.js"; type="text/javascript"></script>
+ <link rel="SHORTCUT ICON" href="/images/favicon.ico">
+ <LINK rel="schema.DC" href="http://purl.org/DC/elements/1.0/">
+ <META name="Description" content="Apache BVal -- Release Process" />
+ <META name="Keywords" content="Apache Bean Validation JSR-303 JavaEE6 " />
+ <META name="Owner" content="bval-dev@incubator.apache.org" />
+ <META name="Robots" content="index, follow" />
+ <META name="Security" content="Public" />
+ <META name="Source" content="wiki template" />
+ <META name="DC.Date" scheme="iso8601" content="2010-05-21" />
+ <META name="DC.Language" scheme="rfc1766" content="en" />
+ <META name="DC.Rights" content="Copyright © 2010, The Apache Software Foundation" />
+ <META http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))'/>
+ <title>
+ Apache BVal
+ </title>
+</head>
+<body>
+
+<table width="100%" cellpadding="0" cellspacing="0">
+ <tr width="100%">
+ <td id="cell-0-0" colspan="2"> </td>
+ <td id="cell-0-1"> </td>
+ <td id="cell-0-2" colspan="2"> </td>
+ </tr>
+ <tr width="100%">
+ <td id="cell-1-0"> </td>
+ <td id="cell-1-1"> </td>
+ <td id="cell-1-2">
+ <div style="padding: 5px;">
+ <div id="banner">
+ <!-- Banner -->
+<p><a name="Banner-Overview"></a></p>
+<table border="0" cellpadding="0" cellspacing="0" width="100%">
+ <tr>
+ <td align="left" nowrap="">
+ <a href="http://incubator.apache.org/bval/" title="Apache BVal">
+ <img border="0" src="/images/check3_71x75.png">
+ </a>
+ </td>
+ <td align="left" class="topbardiv" nowrap="">
+ <a href="/" title="Apache BVal">
+ <img border="0" src="/images/bval_logo.png">
+ </a>
+ </td>
+ <td align="right" nowrap="">
+ <a href="http://www.apache.org/" title="The Apache Software Foundation">
+ <img border="0" src="/images/feather-small.gif">
+ </a>
+ </td>
+ </tr>
+</table>
+ <!-- Banner -->
+ </div>
+ </div>
+ <!--
+ <div id="top-menu">
+ <table border="0" cellpadding="1" cellspacing="0" width="100%">
+ <tr>
+ <td>
+ <div align="left">
+ <a href="/">Home</a>
+ </div>
+ </td>
+ <td>
+ <div align="right">
+$content
+ </div>
+ </td>
+ </tr>
+ </table>
+ </div>
+ -->
+ </td>
+ <td id="cell-1-3"> </td>
+ <td id="cell-1-4"> </td>
+ </tr>
+ <tr width="100%">
+ <td id="cell-2-0" colspan="2"> </td>
+ <td id="cell-2-1">
+ <table>
+ <tr height="100%" valign="top">
+ <td height="100%">
+ <div id="wrapper-menu-page-right">
+ <div id="wrapper-menu-page-top">
+ <div id="wrapper-menu-page-bottom">
+ <div id="menu-page">
+ <!-- NavigationBar -->
+<p><a name="Navigation-Overview"></a></p>
+<h3 id="overview">Overview</h3>
+<ul>
+<li><a href="/board-reports/index.html">Board Reports</a></li>
+<li><a href="http://www.apache.org/licenses/LICENSE-2.0.html">License</a></li>
+<li><a href="/privacy-policy.html">Privacy Policy</a></li>
+</ul>
+<p><a name="Navigation-Community"></a></p>
+<h3 id="community">Community</h3>
+<ul>
+<li><a href="/downloads.html">Downloads</a></li>
+<li><a href="/documentation.html">Documentation</a></li>
+<li><a href="/samples.html">Samples</a></li>
+<li><a href="/roadmap.html">Roadmap</a></li>
+<li><a href="/found-a-bug.html">Found a Bug</a></li>
+<li><a href="/getting-involved.html">Getting Involved</a></li>
+<li><a href="/people.html">People</a></li>
+<li><a href="/mailing-lists.html">Mailing Lists</a></li>
+</ul>
+<p><a name="Navigation-Development"></a></p>
+<h3 id="development">Development</h3>
+<ul>
+<li><a href="https://svn.apache.org/repos/asf/bval/trunk">Source Code</a></li>
+<li><a href="https://issues.apache.org/jira/browse/BVAL">Issue Tracker</a></li>
+<li><a href="/building.html">Building</a></li>
+<li><a href="/coding-standards.html">Coding Standards</a></li>
+<li><a href="/jsr303-tck.html">JSR303 TCK</a></li>
+<li><a href="/release-management.html">Release Management</a></li>
+<li><a href="/automated-builds.html">Automated Builds</a></li>
+</ul>
+<p><a name="Navigation-Sponsorship"></a></p>
+<h3 id="sponsorship">Sponsorship</h3>
+<ul>
+<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsoring Apache</a></li>
+</ul>
+<p><a name="Navigation-Search"></a></p>
+<h3 id="search">Search</h3>
+<p><DIV style="padding: 5px 5px 0px 25px;">
+<FORM action="http://www.google.com/search" method="get" style="font-size:
+10px;">
+ <INPUT name="ie" type="hidden" value="UTF-8"></INPUT>
+ <INPUT name="oe" type="hidden" value="UTF-8"></INPUT>
+ <INPUT maxlength="255" name="q" size="15" type="text" value=""></INPUT>
+ <INPUT name="btnG" type="submit" value="Google Search"></INPUT>
+ <INPUT name="domains" type="hidden" value="bval.apache.org"></INPUT>
+ <INPUT name="sitesearch" type="hidden" value="bval.apache.org"></INPUT>
+</FORM>
+</DIV></p>
+ <!-- NavigationBar -->
+ </div>
+ </div>
+ </div>
+ </div>
+ </td>
+ <td height="100%">
+ <!-- Content -->
+ <div id="BValContent_Release Process" class="wiki-content"><p>We'll be using the <a href="http://repository.apache.org">Apache Nexus repository</a> for
+releasing SNAPSHOT and release artifacts. More details on releasing
+artifacts and using Nexus can be found on the Maven website at
+<a href="http://maven.apache.org/developers/release/apache-release.html">http://maven.apache.org/developers/release/apache-release.html</a>.</p>
+<p><a name="ReleaseProcess-ReleaseSteps"></a></p>
+<h3 id="release-steps">Release Steps</h3>
+<ol>
+<li>
+<p>Environment setup for releasing artifacts (same for <code>SNAPSHOT</code>s and
+releases)</p>
+<ol>
+<li>
+<p>Increase the default Java heap available to Maven (required for Java SE
+6):</p>
+<div class="codehilite"><pre><span class="nb">export </span><span class="nv">MAVEN_OPTS</span><span class="o">=</span><span class="s2">"-Xmx1024m -XX:MaxPermSize=256m"</span>
+</pre></div>
+
+
+</li>
+<li>
+<p>Use the latest Sun 1.6.0 JDK</p>
+</li>
+<li>Use Maven 2.2.1 or later (required for release signing fixes)</li>
+<li>Make sure the <a href="/release-setup.html">Release Setup</a> steps have been performed.</li>
+</ol>
+</li>
+<li>
+<p>Prepare the source for release: </p>
+<ol>
+<li>Clean up JIRA so the <strong>Fix Version</strong> in issues resolved since the last
+ release includes this release version correctly. Also, transition any
+ <strong>Resolved</strong> issues to the <strong>Closed</strong> state.</li>
+<li>
+<p>Update the text files in a working copy of the project root:</p>
+<ol>
+<li>Update the <code>CHANGES.txt</code> based on the Text release reports from JIRA.</li>
+<li>Review and update <code>README.txt</code> if needed.</li>
+<li>
+<p>Commit any changes back to svn:</p>
+<div class="codehilite"><pre>svn commit -m <span class="s2">"updating files for release"</span>
+</pre></div>
+
+
+</li>
+</ol>
+</li>
+<li>
+<p>Stage any Roadmap or Release landing pages on the wiki.</p>
+</li>
+<li>Use <code>mvn rat:check</code> to verify the source has the required headers before
+ trying to release.</li>
+<li>
+<p>Perform a full build and deploy the SNAPSHOT artifacts:</p>
+<div class="codehilite"><pre>mvn clean deploy -Papache-release
+</pre></div>
+
+
+</li>
+<li>
+<p>Run the <a href="/jsr303-tck.html">JSR303 TCK</a> to verify the latest code passes.</p>
+</li>
+<li>Inspect the files in your local target directories to ensure:<ol>
+<li>All jars and zips include: <code>LICENSE</code>, <code>NOTICE</code>, <code>DISCLAIMER</code> files</li>
+<li>The NOTICE files cover all third-party included files (like XSD
+schemas)</li>
+<li>The <code>LICENSE</code> files include any third-party licenses (none at this time)</li>
+<li>All jars/zips/poms have <code>.asc</code> (PGP signature) and <code>.md5</code> files</li>
+</ol>
+</li>
+</ol>
+</li>
+<li>
+<p>For new major releases (like 1.0.0 to 1.1.0)</p>
+<ol>
+<li>
+<p>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:</p>
+<div class="codehilite"><pre>mvn release:branch -DbranchName<span class="o">=</span>1.0.x
+</pre></div>
+
+
+</li>
+</ol>
+</li>
+<li>
+<p>Checkout a clean copy of the trunk/branch to release using command line
+svn:</p>
+<div class="codehilite"><pre>svn checkout https://svn.apache.org/repos/asf/bval/trunk/ 1.0-rc1/
+</pre></div>
+
+
+</li>
+<li>
+<p>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 :</p>
+<ol>
+<li>Release version - take the default - (default 1.0) </li>
+<li>SCM release tag - *DO NOT TAKE THE DEFAULT - (default bval-1.0): : 1.0</li>
+<li>New development version - take the default - (default 1.0.1-SNAPSHOT) </li>
+<li>
+<p><em>optional</em> if you have not specified a GPG passphrase in settings.xml
+you will be prompted for it:</p>
+<div class="codehilite"><pre>mvn -Papache-release release:prepare -DdryRun<span class="o">=</span><span class="nb">true</span>
+</pre></div>
+
+
+<p>Sample output:</p>
+<div class="codehilite"><pre>[INFO] Working directory: /Users/drwoods/bval/1.0-rc1
+[INFO] Checking dependencies and plugins for snapshots ...
+What is the release version for "Apache BVal :: bval-parent (Parent POM)"? (org.apache.bval:bval-parent) 1.0: :
+What is SCM release tag or label for "Apache BVal :: bval-parent (Parent POM)"? (org.apache.bval:bval-parent) bval-parent-1.0: : 1.0
+What is the new development version for "Apache BVal :: bval-parent (Parent POM)"? (org.apache.bval:bval-parent) 1.0.1-SNAPSHOT: :
+[INFO] Transforming 'Apache BVal :: bval-parent (Parent POM)'...
+</pre></div>
+
+
+<p><em>If you cancel a release:prepare before it updates the pom.xml versions,
+ then use the <code>release:clean</code> goal to just remove the extra files that were
+ created.</em></p>
+</li>
+</ol>
+</li>
+<li>
+<p>Verify that the release process completed as expected:</p>
+<ol>
+<li>The release plugin will create <code>pom.xml.tag</code> files which contain the
+ changes that would have been committed to SVN. The only differences between
+ <code>pom.xml.tag</code> and its corresponding <code>pom.xml</code> file should be the version
+ number.</li>
+<li>
+<p>If other formatting changes have been made you should review the changes
+and then commit them:</p>
+<div class="codehilite"><pre>svn commit -m <span class="s2">"fixing formatting for release"</span>
+</pre></div>
+
+
+</li>
+<li>
+<p>Assuming the <code>.tag</code> files look OK you may proceed and do any other
+validation you feel necessary. The following list may be helpful:</p>
+<ol>
+<li>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.</li>
+<li><a href="#ReleaseProcess-Verifyingreleasesignatures">Verify signatures</a></li>
+<li>If you have access to the <a href="/jsr303-tck.html">JSR303 TCK</a>, run it.</li>
+</ol>
+</li>
+<li>
+<p>Once any failures or required updates have been committed to svn,
+rollback the release prepare files:</p>
+<div class="codehilite"><pre>mvn -Papache-release release:rollback
+</pre></div>
+
+
+</li>
+</ol>
+</li>
+<li>
+<p>Prepare the release</p>
+<p>Run the <code>release:prepare</code> step for real this time. You'll be prompted
+for the same version information and optionally your GPG passphrase again.</p>
+<p><strong>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 <a href="http://jira.codehaus.org/browse/MJAR-68">http://jira.codehaus.org/browse/MJAR-68</a>
+and <a href="http://jira.codehaus.org/browse/MRELEASE-285">http://jira.codehaus.org/browse/MRELEASE-285</a>.</strong></p>
+<div class="codehilite"><pre>mvn release:prepare -Papache-release -DskipTests<span class="o">=</span><span class="nb">true</span> -DpreparationGoals<span class="o">=</span><span class="s2">"clean install"</span>
+</pre></div>
+
+
+</li>
+<li>
+<p>Backup (zip or tar) your local release candidate directory in case you
+need to rollback the release after the next step is performed.</p>
+<div class="codehilite"><pre><span class="nb">cd</span> ..
+tar -czf 1.0-rc1.tar.gz 1.0-rc1/
+<span class="nb">cd </span>1.0-rc1
+</pre></div>
+
+
+</li>
+<li>
+<p>Perform the release:</p>
+<ol>
+<li>
+<p>This step will create a maven staging repository and site for use in
+ testing and voting. You will be prompted for your <strong>repository.apache.org</strong>
+ and <strong>people.apache.org</strong> password several times if you have not added
+ server profiles to your <code>settings.xml</code>.
+ See <a href="/release-setup.html">Release Setup</a> for more information. </p>
+<div class="codehilite"><pre>mvn release:perform -Papache-release -Duser.name<span class="o">=[</span>your_apache_uid<span class="o">]</span>
+</pre></div>
+
+
+</li>
+</ol>
+<p><strong>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.</strong></p>
+<ol>
+<li>The maven-release-plugin is configured with goals <code>deploy site
+site:deploy</code> and will deploy the site files to a <code>staging-site</code> directory on
+<strong>people.apache.org</strong>.</li>
+<li>Verify the release artifacts:</li>
+<li>Verify the HTML links in staging-site/index.html are correct</li>
+<li>Verify the staged artifacts in the nexus repo:<ol>
+<li><a href="https://repository.apache.org/index.html">https://repository.apache.org/index.html</a></li>
+<li><strong>Enterprise --> Staging</strong></li>
+<li><strong>Staging tab --> Name column --> org.apache.bval</strong></li>
+<li>Navigate through the artifact tree and make sure that all <code>javadoc</code>,
+ <code>sources</code>, <code>tests</code> jars, ... have <code>.asc</code> (GPG signature) and <code>.md5</code>
+ files (see <a href="http://people.apache.org/~henkp/repo/faq.html">Repository FAQ</a> and <a href="http://www.apache.org/dev/release-signing.html#openpgp-ascii-detach-sig">Detached Signatures</a>).</li>
+</ol>
+</li>
+<li>Close the nexus staging repo:<ol>
+<li><a href="https://repository.apache.org/index.html">https://repository.apache.org/index.html</a></li>
+<li><strong>Enterprise --> Staging</strong></li>
+<li><strong>Staging tab --> Name column --> org.apache.bval</strong></li>
+<li>Right click on the open <code>org.apache.bval-XXX</code> staging repo
+ and select <strong>Close</strong>.</li>
+</ol>
+</li>
+</ol>
+</li>
+<li>
+<p>Put the release candidate up for a vote:</p>
+<ol>
+<li>
+<p>Create a <code>VOTE</code> email thread on <a href="mailto:dev@bval.apache.org">bval-dev</a> to record votes as replies, e.g.:</p>
+<div class="codehilite"><pre>To: dev@bval.apache.org
+Subject: [VOTE] Apache BVal 1.0 Release Candidate
+
+I've created a 1.0 release candidate, with the following artifacts up for a vote:
+
+SVN source tag (r950702):
+https://svn.apache.org/repos/asf/bval/tags/1.0/
+
+Maven staging repo:
+https://repository.apache.org/content/repositories/orgapachebval-020/
+
+Source release:
+https://repository.apache.org/content/repositories/orgapachebval-020/org/apache/bval/bval-parent/1.0/bval-parent-1.0-source-release.zip
+
+Javadoc staging site:
+http://people.apache.org/~mbenson/bval/1.0/staging-site/apidocs/
+
+PGP release keys (signed using D018E6B1):
+https://svn.apache.org/repos/asf/bval/KEYS
+
+Vote will be open for 72 hours.
+
+[ ] +1 approve
+[ ] +0 no opinion
+[ ] -1 disapprove (and reason why)
+</pre></div>
+
+
+</li>
+<li>
+<p>Create a DISCUSS email thread on bval-dev@ for any vote questions, e.g.:</p>
+<div class="codehilite"><pre>To: dev@bval.apache.org
+Subject: [DISCUSS] Apache BVal 1.0 Release Candidate
+
+Discussion thread for vote on 1.0 release candidate, with SVN source tag (r999999).
+
+For more information on the release process, check out http://www.apache.org/dev/release.html .
+
+Some of the things to check before voting are:
+- does "mvn apache-rat:check" pass on the source
+- can you build the contents of source-release.zip and svn tag
+- do all of the staged jars/zips contain the required LICENSE, NOTICE and DISCLAIMER files
+- are all of the staged jars signed and the signature verifiable
+- is the signing key in the project's KEYS file and on a public server
+- does the release pass the TCK
+</pre></div>
+
+
+</li>
+<li>
+<p>Perform a review of the release and cast your vote. For more details
+ on Apache releases see
+ <a href="http://www.apache.org/dev/release.html">http://www.apache.org/dev/release.html</a>.</p>
+</li>
+<li>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 <a href="#ReleaseProcess-RecoveringFromAVetoedRelease">Recovering from a vetoed release</a>.</li>
+<li>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:<ol>
+<li>Reply to the initial email prepending <code>[RESULT]</code> to the original subject</li>
+<li>Include a list of every binding +1, 0 or -1 vote.</li>
+</ol>
+</li>
+</ol>
+</li>
+<li>
+<p>Finalizing a release</p>
+<ol>
+<li>Promote the staged nexus artifacts:<ol>
+<li><a href="https://repository.apache.org/index.html">https://repository.apache.org/index.html</a></li>
+<li><strong>Enterprise --> Staging</strong></li>
+<li><strong>Staging tab --> Name column --> org.apache.bval</strong></li>
+<li>Right click on the closed <code>org.apache.bval-XXX</code> staging repo and select <strong>Promote</strong>.</li>
+</ol>
+</li>
+<li>
+<p><em>Pending removal or amendment: site not maven-managed</em> Copy the staged site over to our website area:</p>
+<div class="codehilite"><pre>ssh <span class="k">${</span><span class="nv">user</span><span class="p">.name</span><span class="k">}</span>@people.apache.org
+mkdir /www/bval.apache.org/<span class="k">${</span><span class="nv">project</span><span class="p">.version</span><span class="k">}</span>
+cp -R ~/public_html/bval/<span class="k">${</span><span class="nv">project</span><span class="p">.version</span><span class="k">}</span>/staging-site/* /www/bval.apache.org/<span class="k">${</span><span class="nv">project</span><span class="p">.version</span><span class="k">}</span>
+<span class="se">\#</span> Make sure all the copied files have g+rw <span class="nb">set </span>and only o+r <span class="nb">set</span>
+<span class="nb">cd</span> /www/bval.apache.org
+find . -user <span class="k">${</span><span class="nv">user</span><span class="p">.name</span><span class="k">}</span> -type f | xargs chmod 664
+find . -user <span class="k">${</span><span class="nv">user</span><span class="p">.name</span><span class="k">}</span> -type d | xargs chmod 775
+</pre></div>
+
+
+</li>
+<li>
+<p>Update the <em>Documentation</em> wiki page to point to the new apidocs:</p>
+<div class="codehilite"><pre>http://bval.apache.org/${project.version}/apidocs/
+</pre></div>
+
+
+</li>
+<li>
+<p>Copy the distribution artifacts over to the distribution area:</p>
+<div class="codehilite"><pre>ssh <span class="k">${</span><span class="nv">user</span><span class="p">.name</span><span class="k">}</span>@people.apache.org
+mkdir /www/www.apache.org/dist/bval/<span class="k">${</span><span class="nv">project</span><span class="p">.version</span><span class="k">}</span>
+<span class="nb">cd</span> /www/www.apache.org/dist/bval/<span class="k">${</span><span class="nv">project</span><span class="p">.version</span><span class="k">}</span>
+wget https://repository.apache.org/content/repositories/releases/org/apache/bval/bval-parent/<span class="k">${</span><span class="nv">project</span><span class="p">.version</span><span class="k">}</span>/bval-parent-<span class="k">${</span><span class="nv">project</span><span class="p">.version</span><span class="k">}</span>-source-release.zip
+wget https://repository.apache.org/content/repositories/releases/org/apache/bval/bval-parent/<span class="k">${</span><span class="nv">project</span><span class="p">.version</span><span class="k">}</span>/bval-parent-<span class="k">${</span><span class="nv">project</span><span class="p">.version</span><span class="k">}</span>-source-release.zip.asc
+wget https://repository.apache.org/content/repositories/releases/org/apache/bval/bval-parent/<span class="k">${</span><span class="nv">project</span><span class="p">.version</span><span class="k">}</span>/bval-parent-<span class="k">${</span><span class="nv">project</span><span class="p">.version</span><span class="k">}</span>-source-release.zip.md5
+wget https://repository.apache.org/content/repositories/releases/org/apache/bval/bval-parent/<span class="k">${</span><span class="nv">project</span><span class="p">.version</span><span class="k">}</span>/bval-parent-<span class="k">${</span><span class="nv">project</span><span class="p">.version</span><span class="k">}</span>-source-release.zip.sha1
+<span class="c"># Make sure all the copied files have g+rw set and only o+r set</span>
+find . -user <span class="k">${</span><span class="nv">user</span><span class="p">.name</span><span class="k">}</span> -type f | xargs chmod 664
+find . -user <span class="k">${</span><span class="nv">user</span><span class="p">.name</span><span class="k">}</span> -type d | xargs chmod 775
+<span class="c"># Note: All of the artifacts are in the maven repos, but we may create an assembly to publish in future releases</span>
+</pre></div>
+
+
+</li>
+<li>
+<p>Update the <em>Downloads</em> wiki page to point to the new release artifacts:</p>
+<div class="codehilite"><pre>http://www.apache.org/dyn/closer.cgi/bval/${project.version}/
+http://repo1.maven.org/maven2/org/apache/bval/${artifactId}/${project.version}/
+</pre></div>
+
+
+</li>
+<li>
+<p>Update the <a href="https://issues.apache.org/jira/secure/project/ManageVersions.jspa?pid=12311080">JIRA versions</a>
+ page to mark the version as <strong>Released</strong>, 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.</p>
+</li>
+</ol>
+</li>
+<li>
+<p>Announcing the release</p>
+<ol>
+<li>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.</li>
+<li>Make a <a href="http://cwiki.apache.org/confluence/pages/createblogpost.action?spaceKey=BVal">news announcement</a> on the BVal wiki.</li>
+<li>Make an announcement about the release on the
+ <a href="mailto:users@bval.apache.org">bval-users</a>,
+ <a href="mailto:dev@bval.apache.org">bval-dev</a>, and
+ <a href="mailto:announce@apache.org">announce@apache.org</a> lists as per
+ <a href="http://www.apache.org/foundation/mailinglists.html#foundation-announce]">the Apache Announcement Mailing Lists page</a></li>
+</ol>
+</li>
+</ol>
+<p><a name="ReleaseProcess-RecoveringFromAVetoedRelease"></a></p>
+<h3 id="recovering-from-a-vetoed-release">Recovering from a vetoed release</h3>
+<ol>
+<li>
+<p>Reply to the initial vote email prepending <code>[CANCELED]</code> to the original subject.</p>
+</li>
+<li>
+<p>Rollback the version upgrades in trunk by <em>either</em>:</p>
+<ol>
+<li>
+<p>Restore the 0.1-rc1.tar.gz and run</p>
+<div class="codehilite"><pre>mvn -Papache-release release:rollback
+</pre></div>
+
+
+<p>, <em>or</em>:</p>
+</li>
+<li>
+<p>Manually revert the versions in trunk to the prior version and commit</p>
+</li>
+</ol>
+</li>
+<li>
+<p>Delete the svn tag created by the <code>release:perform</code> step:</p>
+<div class="codehilite"><pre>svn rm https://svn.apache.org/repos/asf/bval/tags/1.0 -m <span class="s2">"deleting tag from rolled back release"</span>
+</pre></div>
+
+
+</li>
+<li>
+<p>Drop the nexus staging repo:</p>
+<ol>
+<li><a href="https://repository.apache.org/index.html">https://repository.apache.org/index.html</a></li>
+<li><strong>Enterprise --> Staging</strong></li>
+<li><strong>Staging tab --> Name column --> org.apache.bval</strong></li>
+<li>Right click on the closed <code>org.apache.bval-XXX</code> staging repo and select <strong>Drop</strong>.</li>
+</ol>
+</li>
+<li>
+<p>Remove the staged site:</p>
+<div class="codehilite"><pre>ssh <span class="k">${</span><span class="nv">user</span><span class="p">.name</span><span class="k">}</span>@people.apache.org
+<span class="nb">cd</span> ~/public_html/bval
+rm -fr <span class="k">${</span><span class="nv">project</span><span class="p">.version</span><span class="k">}</span>
+</pre></div>
+
+
+</li>
+<li>
+<p>Make the required updates that caused the vote to be canceled.</p>
+</li>
+<li>Spin another release candidate!</li>
+</ol>
+<p><a name="ReleaseProcess-Verifyingreleasesignatures"></a></p>
+<h3 id="verifying-release-signatures">Verifying release signatures</h3>
+<p>On unix platforms the following command can be executed:</p>
+<div class="codehilite"><pre><span class="k">for </span>file in <span class="sb">`</span>find . -type f -iname <span class="s1">'*.asc'</span><span class="sb">`</span>
+<span class="k">do</span>
+<span class="k"> </span>gpg --verify <span class="k">${</span><span class="nv">file</span><span class="k">}</span>
+<span class="k">done</span>
+</pre></div>
+
+
+<p>You'll need to look at the output to ensure it contains only good signatures:</p>
+<div class="codehilite"><pre>gpg: Good signature from ...
+gpg: Signature made ...
+</pre></div></div>
+ <!-- Content -->
+ </td>
+ </tr>
+ </table>
+ </td>
+ <td id="cell-2-2" colspan="2"> </td>
+ </tr>
+ <tr width="100%">
+ <td id="cell-3-0"> </td>
+ <td id="cell-3-1"> </td>
+ <td id="cell-3-2">
+ <div id="footer">
+ <!-- Footer -->
+ <div id="site-footer">
+ </div>
+ <!-- Footer -->
+ </div>
+ </td>
+ <td id="cell-3-3"> </td>
+ <td id="cell-3-4"> </td>
+ </tr>
+ <tr width="100%">
+ <td id="cell-4-0" colspan="2"> </td>
+ <td id="cell-4-1">
+ <div id="footer-legal">
+Copyright (C) 2010-2012 The Apache Software Foundation. Licensed under <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License 2.0</a>.<br />
+Apache and the Apache feather logo are trademarks of The Apache Software Foundation.<br />
+Other names may be trademarks of their respective owners.
+ </div>
+ </td>
+ <td id="cell-4-2" colspan="2"> </td>
+ </tr>
+ <tr width="100%">
+ <td id="cell-4-0" colspan="2"> </td>
+ <td id="cell-4-1"> </td>
+ <td id="cell-4-2" colspan="2"> </td>
+ </tr>
+</table>
+</body>
+</html>
Added: websites/staging/bval/trunk/content/release-setup.cwiki
==============================================================================
--- websites/staging/bval/trunk/content/release-setup.cwiki (added)
+++ websites/staging/bval/trunk/content/release-setup.cwiki Sat Mar 10 22:51:09 2012
@@ -0,0 +1,120 @@
+
+These setup steps only need to be performed on a particular machine once.
+{info}Developers using Linux workstations can skip over the references to Cygwin. If using Windows, install cygwin, including *Utils/gnupg* and *Net/openssh* packages.
+{info}
+
+h3. Create and install a SSH key
+
+# Open a shell window. If using Windows, open a cygwin window.
+# Use ssh-keygen to create an SSH key.
+{note}Follow the latest steps and guides on the ASF website at [http://www.apache.org/dev/openpgp.html#generate-key] as you need to disable using SHA1 and new keys should be 4096 bits.{note}
+{code:none}
+$ ssh-keygen -t dsa -b 4096
+{code}
+* Program defaults should be fine. No passphrase is required for the ssh key generation. The keys will be saved in ~/.ssh/id_dsa (private) and ~/.ssh/id_dsa.pub (public).
+{info} See [Authenticating By Public Key (OpenSSH)|http://www.networknewz.com/networknewz-10-20030707AuthenticatingbyPublicKeyOpenSSH.html] for a good description on why and how to perform this task.
+{info}
+# {{scp}} your SSH public key ~/.ssh/id_dsa.pub created in last step to ~/id_dsa.pub on people.apache.org.
+{code:none}
+$ cd ~/.ssh
+$ scp id_dsa.pub <your userid>@people.apache.org:id_dsa.pub
+$ You will be prompted for your password.
+{code}
+# Use ssh to login to people.apache.org
+{code:none}
+$ cd ~
+$ ssh <your userid>@people.apache.org
+{code}
+* At this point, you will still be prompted for your password.
+# Create a ~/.ssh folder in your home directory on people.apache.org and change its file mode to 700.
+{code:none}
+$ mkdir ~/.ssh
+$ chmod 700 ~/.ssh
+{code}
+# Move or append ~/id_dsa.pub to ~/.ssh/authorized_keys and change its file mode to 600.
+{code:none}
+$ mv ~/id_dsa.pub ~/.ssh/authorized_keys
+$ chmod 600 ~/.ssh/authorized_keys
+{code}
+{info}
+* Each public key in the {{authorized_keys}} spans only one line.
+** For example: "{{ssh-dss AAAAB3NzaC1kc3MAAA ..... agBmmfZ9uAbSqA== dsa-key-20071107}}"
+* '#' in the first column is a comment line.
+{info}
+# Exit out of this ssh session.
+# Start a new ssh session. No login should be required this time due to the private ssh key on your local box matching up with the public ssh key in your home directory (~/.ssh).
+{code:none}
+$ ssh <your userid>@people.apache.org
+{code}
+{info}
+If you are still prompted for a password, then you have not set up the ssh keys properly. Review the steps above and ensure that all of the steps were followed properly. Or, maybe the instructions are still not quite right and they still need some adjusting. In that case, please update the instructions accordingly. :-)
+{info}
+
+
+h3. Create a GPG key
+
+# Open a shell window. If using Windows, open a cygwin window.
+# Generate a key-pair with gpg, using default key kind ("DSA and Elgamal") and ELG-E keys size (2048).
+{code:none}
+$ gpg --gen-key
+{code}
+* The program's default values should be fine. For the "Real Name" enter your full name (ie. Stan Programmer). For the "e-mail address" enter your apache address (ie. sprogrammer@apache.org). You will also be required to enter a "passphrase" for the GPG key generation. Keep track of this as you will need this for the Release processing.
+{info}
+* The generated keys are stored in $HOME/.gnupg or %HOME%\Application Data\gnupg subdirectory.
+* Save the content in this subdirectory to a safe media. This contains your private key used to sign all the BVAL release materials.
+{info}
+# Backup your cygwin home directory to another media ||
+# Add your public key to {{[https://svn.apache.org/repos/asf/incubator/bval/KEYS]}} and {{http://www.apache.org/dist/incubator/bval/KEYS}}. See the commands describe at the beginning of this KEYS file to perform this task. The gpg key-pair is used to sign the published artifacts for the BVAL releases.
+{code:none}
+$ gpg --list-sigs <Real Name> && gpg --armor -- export <Real Name>
+{code}
+{info}The {{[https://svn.apache.org/repos/asf/incubator/bval/KEYS]}} file is updated via normal svn commit procedures. The one under w.a.o/dist/ has to be manually updated from svn.
+{info}
+# Submit your public key to a key server. E.g. [http://pgp.surfnet.nl:11371/] or [http://pgp.mit.edu/]||
+# Following the instructions in [http://people.apache.org/~henkp/trust/] and ask multiple (at least 3) current Apache committers to sign your public key.
+
+h3. Update Maven settings for our servers
+
+# Create a settings.xml under .m2
+| | {code:xml|title=settings.xml|borderStyle=solid}
+<settings xmlns="http://maven.apache.org/POM/4.0.0"
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd">
+ <servers>
+ <!-- SCP settings for people.apache.org -->
+ <server>
+ <id>people.apache.org</id>
+ <username>$USERNAME</username>
+ <privateKey>$PATH_TO_PRIVATE_KEY</privateKey>
+ <passphrase>$SSH_PASSPHRASE</passphrase>
+ <directoryPermissions>775</directoryPermissions>
+ <filePermissions>644</filePermissions>
+ <!-- following is only for Windows only
+ <configuration>
+ <sshExecutable>plink</sshExecutable>
+ <scpExecutable>pscp</scpExecutable>
+ <scpArgs>-2Bp</scpArgs>
+ <sshArgs>-2</sshArgs>
+ </configuration>
+ -->
+ </server>
+ <!-- ASF Nexus settings -->
+ <server>
+ <id>apache.snapshots.https</id>
+ <username>$USERNAME</username>
+ <password>$APACHE_LDAP_PWD</password>
+ </server>
+ <server>
+ <id>apache.releases.https</id>
+ <username>$USERNAME</username>
+ <password>$APACHE_LDAP_PWD</password>
+ </server>
+ </servers>
+</settings>
+{code}
+{info}
+* {{$USERNAME}} is the remote username on people.apache.org, not your local userid.
+* {{$PATH_TO_PRIVATE_KEY}} is the path to the private key generated for ssh. E.g. /home/yourLocalUserId/.ssh/id_dsa. For Windows' cygwin users, you will need to enter the full cygwin path: /cygdrive/c/cygwin/home/yourLocalUserId/.ssh/id_dsa.
+* {{$SSH_PASSPHRASE}} for the supplied {{$PATH_TO_PRIVATE_KEY}}. If you don't use this in your settings.xml file, then you will be prompted for it during the Release processing.
+* {{$APACHE_LDAP_PWD}} is your Apache LDAP password, which is shared between SVN and password login for people.apache.org.
+{info}
Added: websites/staging/bval/trunk/content/release-setup.html
==============================================================================
--- websites/staging/bval/trunk/content/release-setup.html (added)
+++ websites/staging/bval/trunk/content/release-setup.html Sat Mar 10 22:51:09 2012
@@ -0,0 +1,395 @@
+
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<!--
+Licensed to the Apache Software Foundation (ASF) under one
+or more contributor license agreements. See the NOTICE file
+distributed with this work for additional information
+regarding copyright ownership. The ASF licenses this file
+to you under the Apache License, Version 2.0 (the
+"License"); you may not use this file except in compliance
+with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing,
+software distributed under the License is distributed on an
+"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+KIND, either express or implied. See the License for the
+specific language governing permissions and limitations
+under the License.
+-->
+<html>
+<head>
+ <META http-equiv="Content-Type" content="text/html;charset=UTF-8" />
+ <link type="text/css" rel="stylesheet" href="/resources/site.css";></link>
+ <link type="text/css" rel="stylesheet" href="/resources/code.css";></link>
+ <script src="/resources/space.js"; type="text/javascript"></script>
+ <link rel="SHORTCUT ICON" href="/images/favicon.ico">
+ <LINK rel="schema.DC" href="http://purl.org/DC/elements/1.0/">
+ <META name="Description" content="Apache BVal -- Release Setup" />
+ <META name="Keywords" content="Apache Bean Validation JSR-303 JavaEE6 " />
+ <META name="Owner" content="bval-dev@incubator.apache.org" />
+ <META name="Robots" content="index, follow" />
+ <META name="Security" content="Public" />
+ <META name="Source" content="wiki template" />
+ <META name="DC.Date" scheme="iso8601" content="2010-05-21" />
+ <META name="DC.Language" scheme="rfc1766" content="en" />
+ <META name="DC.Rights" content="Copyright © 2010, The Apache Software Foundation" />
+ <META http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))'/>
+ <title>
+ Apache BVal
+ </title>
+</head>
+<body>
+
+<table width="100%" cellpadding="0" cellspacing="0">
+ <tr width="100%">
+ <td id="cell-0-0" colspan="2"> </td>
+ <td id="cell-0-1"> </td>
+ <td id="cell-0-2" colspan="2"> </td>
+ </tr>
+ <tr width="100%">
+ <td id="cell-1-0"> </td>
+ <td id="cell-1-1"> </td>
+ <td id="cell-1-2">
+ <div style="padding: 5px;">
+ <div id="banner">
+ <!-- Banner -->
+<p><a name="Banner-Overview"></a></p>
+<table border="0" cellpadding="0" cellspacing="0" width="100%">
+ <tr>
+ <td align="left" nowrap="">
+ <a href="http://incubator.apache.org/bval/" title="Apache BVal">
+ <img border="0" src="/images/check3_71x75.png">
+ </a>
+ </td>
+ <td align="left" class="topbardiv" nowrap="">
+ <a href="/" title="Apache BVal">
+ <img border="0" src="/images/bval_logo.png">
+ </a>
+ </td>
+ <td align="right" nowrap="">
+ <a href="http://www.apache.org/" title="The Apache Software Foundation">
+ <img border="0" src="/images/feather-small.gif">
+ </a>
+ </td>
+ </tr>
+</table>
+ <!-- Banner -->
+ </div>
+ </div>
+ <!--
+ <div id="top-menu">
+ <table border="0" cellpadding="1" cellspacing="0" width="100%">
+ <tr>
+ <td>
+ <div align="left">
+ <a href="/">Home</a>
+ </div>
+ </td>
+ <td>
+ <div align="right">
+$content
+ </div>
+ </td>
+ </tr>
+ </table>
+ </div>
+ -->
+ </td>
+ <td id="cell-1-3"> </td>
+ <td id="cell-1-4"> </td>
+ </tr>
+ <tr width="100%">
+ <td id="cell-2-0" colspan="2"> </td>
+ <td id="cell-2-1">
+ <table>
+ <tr height="100%" valign="top">
+ <td height="100%">
+ <div id="wrapper-menu-page-right">
+ <div id="wrapper-menu-page-top">
+ <div id="wrapper-menu-page-bottom">
+ <div id="menu-page">
+ <!-- NavigationBar -->
+<p><a name="Navigation-Overview"></a></p>
+<h3 id="overview">Overview</h3>
+<ul>
+<li><a href="/board-reports/index.html">Board Reports</a></li>
+<li><a href="http://www.apache.org/licenses/LICENSE-2.0.html">License</a></li>
+<li><a href="/privacy-policy.html">Privacy Policy</a></li>
+</ul>
+<p><a name="Navigation-Community"></a></p>
+<h3 id="community">Community</h3>
+<ul>
+<li><a href="/downloads.html">Downloads</a></li>
+<li><a href="/documentation.html">Documentation</a></li>
+<li><a href="/samples.html">Samples</a></li>
+<li><a href="/roadmap.html">Roadmap</a></li>
+<li><a href="/found-a-bug.html">Found a Bug</a></li>
+<li><a href="/getting-involved.html">Getting Involved</a></li>
+<li><a href="/people.html">People</a></li>
+<li><a href="/mailing-lists.html">Mailing Lists</a></li>
+</ul>
+<p><a name="Navigation-Development"></a></p>
+<h3 id="development">Development</h3>
+<ul>
+<li><a href="https://svn.apache.org/repos/asf/bval/trunk">Source Code</a></li>
+<li><a href="https://issues.apache.org/jira/browse/BVAL">Issue Tracker</a></li>
+<li><a href="/building.html">Building</a></li>
+<li><a href="/coding-standards.html">Coding Standards</a></li>
+<li><a href="/jsr303-tck.html">JSR303 TCK</a></li>
+<li><a href="/release-management.html">Release Management</a></li>
+<li><a href="/automated-builds.html">Automated Builds</a></li>
+</ul>
+<p><a name="Navigation-Sponsorship"></a></p>
+<h3 id="sponsorship">Sponsorship</h3>
+<ul>
+<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsoring Apache</a></li>
+</ul>
+<p><a name="Navigation-Search"></a></p>
+<h3 id="search">Search</h3>
+<p><DIV style="padding: 5px 5px 0px 25px;">
+<FORM action="http://www.google.com/search" method="get" style="font-size:
+10px;">
+ <INPUT name="ie" type="hidden" value="UTF-8"></INPUT>
+ <INPUT name="oe" type="hidden" value="UTF-8"></INPUT>
+ <INPUT maxlength="255" name="q" size="15" type="text" value=""></INPUT>
+ <INPUT name="btnG" type="submit" value="Google Search"></INPUT>
+ <INPUT name="domains" type="hidden" value="bval.apache.org"></INPUT>
+ <INPUT name="sitesearch" type="hidden" value="bval.apache.org"></INPUT>
+</FORM>
+</DIV></p>
+ <!-- NavigationBar -->
+ </div>
+ </div>
+ </div>
+ </div>
+ </td>
+ <td height="100%">
+ <!-- Content -->
+ <div id="BValContent_Release Setup" class="wiki-content"><p>These setup steps only need to be performed on a particular machine once.
+<em>Note</em>: Developers using Linux workstations can skip over the references to
+<a href="http://www.cygwin.com/">Cygwin</a>. If using Windows, install cygwin, including <code>Utils/gnupg</code> and
+<code>Net/openssh</code> packages.</p>
+<p><a name="ReleaseSetup-CreateandinstallaSSHkey"></a></p>
+<h3 id="create-and-install-a-ssh-key">Create and install a SSH key</h3>
+<ol>
+<li>Open a shell window. If using Windows, open a cygwin window.</li>
+<li>
+<p>Use <code>ssh-keygen</code> to create an SSH key.
+ <em>Note</em>: Follow the latest steps and guides on the ASF website at
+ <a href="http://www.apache.org/dev/openpgp.html#generate-key">http://www.apache.org/dev/openpgp.html#generate-key</a>
+ as you need to disable using SHA1 and new keys should be 4096 bits.</p>
+<div class="codehilite"><pre>ssh-keygen -t dsa -b 4096
+</pre></div>
+
+
+<p>Program defaults should be fine. No passphrase is required for the <code>ssh</code>
+key generation. The keys will be saved in <code>~/.ssh/id_dsa</code> (private) and
+<code>~/.ssh/id_dsa.pub</code> (public).</p>
+<p><em>See <a href="http://www.networknewz.com/networknewz-10-20030707AuthenticatingbyPublicKeyOpenSSH.html">Authenticating By Public Key (OpenSSH)</a>
+for a good description on why and how to perform this task.</em></p>
+</li>
+<li>
+<p><code>scpl</code> your SSH public key <code>~/.ssh/id_dsa.pub</code> created in last step to
+ <code>~/id_dsa.pub</code> on <code>people.apache.org</code>:</p>
+<div class="codehilite"><pre><span class="nb">cd</span> ~/.ssh
+scp id_dsa.pub <your userid>@people.apache.org:id_dsa.pub
+</pre></div>
+
+
+<p>You will be prompted for your password.</p>
+</li>
+<li>
+<p>Use <code>ssh</code> to log into <code>people.apache.org</code>:</p>
+<div class="codehilite"><pre><span class="nb">cd</span> ~
+ssh <your userid>@people.apache.org
+</pre></div>
+
+
+<p>At this point, you will still be prompted for your password.</p>
+</li>
+<li>
+<p>Create a <code>.ssh</code> folder in your home directory (<code>~</code>) on <code>people.apache.org</code> and
+ change its file mode to <code>700</code>
+ (owner read/write/execute, no permissions granted to anyone else):</p>
+<div class="codehilite"><pre>mkdir ~/.ssh
+chmod 700 ~/.ssh
+</pre></div>
+
+
+</li>
+<li>
+<p>Move or append <code>~/id_dsa.pub</code> to <code>~/.ssh/authorized_keys</code> and change its file
+mode to <code>600</code> (owner read/write, no permissions granted to anyone else):</p>
+<div class="codehilite"><pre>mv ~/id_dsa.pub ~/.ssh/authorized_keys
+chmod 600 ~/.ssh/authorized_keys
+</pre></div>
+
+
+<p>Each public key in the <code>authorized_keys</code> file spans only one line, e.g.:</p>
+<div class="codehilite"><pre>ssh-dss AAAAB3NzaC1kc3MAAA ..... agBmmfZ9uAbSqA==dsa-key-20071107
+</pre></div>
+
+
+<p>(any line with <code>'#'</code> in the first column is a comment line)</p>
+</li>
+<li>
+<p>Exit out of this <code>ssh</code> session.</p>
+</li>
+<li>
+<p>Start a new <code>ssh</code> session. No login should be required this time due to
+ the private key on your local box matching up with the public key
+ in your home directory (<code>~/.ssh</code>):</p>
+<div class="codehilite"><pre>ssh <span class="k">${</span><span class="nv">USER</span><span class="k">}</span>@people.apache.org
+</pre></div>
+
+
+<p>If you are still prompted for a password, then you have not set up the
+keys properly. Review the steps above and ensure that all of the steps
+were followed properly. Or, maybe the instructions are still not quite
+right and they still need some adjusting. In that case, please update the
+instructions accordingly. :-)</p>
+</li>
+</ol>
+<p><a name="ReleaseSetup-CreateaGPGkey"></a></p>
+<h3 id="create-a-gpg-key">Create a GPG key</h3>
+<ol>
+<li>Open a shell window. If using Windows, open a cygwin window.</li>
+<li>
+<p>Generate a key-pair with <code>gpg</code>, using default key kind ("DSA and Elgamal")
+and ELG-E keys size (2048).</p>
+<div class="codehilite"><pre>gpg --gen-key
+</pre></div>
+
+
+<p>The program's default values should be fine. For the "Real Name" enter
+your full name (ie. Stan Programmer). For the "e-mail address" enter your
+apache address (ie. sprogrammer@apache.org). You will also be required to
+enter a "passphrase" for the GPG key generation. Keep track of this as you
+will need this for the Release processing.</p>
+<p><em>The generated keys are stored in <code>$HOME/.gnupg</code> or <code>%HOME%\Application
+Data\gnupg</code> directory.</em>
+<em>Save the content in this directory to a safe medium. This contains your
+private key used to sign all the BVal release materials.</em></p>
+</li>
+<li>
+<p>Back up your cygwin home directory to some other medium.</p>
+</li>
+<li>
+<p>Add your public key to <a href="https://svn.apache.org/repos/asf/bval/KEYS">https://svn.apache.org/repos/asf/bval/KEYS</a>
+ and <a href="http://www.apache.org/dist/bval/KEYS">http://www.apache.org/dist/bval/KEYS</a>. See the commands
+described at the beginning of this KEYS file to perform this task. The gpg
+key-pair is used to sign the published artifacts for the BVAL releases. </p>
+<div class="codehilite"><pre>gpg --list-sigs <Real Name> <span class="o">&&</span> gpg --armor -- <span class="nb">export</span> <Real Name>
+</pre></div>
+
+
+<p><em>The <a href="https://svn.apache.org/repos/asf/bval/KEYS">https://svn.apache.org/repos/asf/bval/KEYS</a>
+file is updated via normal svn commit procedures. The one at
+<a href="http://www.apache.org/dist/bval/KEYS">http://www.apache.org/dist/bval/KEYS</a> must be manually updated from svn.</em></p>
+</li>
+<li>
+<p>Submit your public key to a key server, e.g. <a href="http://pgp.surfnet.nl:11371/">http://pgp.surfnet.nl:11371/</a>
+ or <a href="http://pgp.mit.edu/">http://pgp.mit.edu/</a>.</p>
+</li>
+<li>
+<p>Following the instructions in <a href="http://people.apache.org/~henkp/trust/">http://people.apache.org/~henkp/trust/</a> and
+ ask multiple (at least 3) current Apache committers to sign your public key.</p>
+</li>
+</ol>
+<p><a name="ReleaseSetup-UpdateMavensettingsforourservers"></a></p>
+<h3 id="update-maven-settings-for-our-servers">Update Maven settings for our servers</h3>
+<p>Create a <code>settings.xml</code> under <code>.m2</code>:</p>
+<div class="codehilite"><pre><span class="nt"><settings</span> <span class="na">xmlns=</span><span class="s">"http://maven.apache.org/POM/4.0.0"</span>
+ <span class="na">xmlns:xsi=</span><span class="s">"http://www.w3.org/2001/XMLSchema-instance"</span>
+ <span class="na">xsi:schemaLocation=</span><span class="s">"http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd"</span><span class="nt">></span>
+ <span class="nt"><servers></span>
+ <span class="c"><!-- SCP settings for people.apache.org --></span>
+ <span class="nt"><server></span>
+ <span class="nt"><id></span>people.apache.org<span class="nt"></id></span>
+ <span class="nt"><username></span>$USERNAME<span class="nt"></username></span>
+ <span class="nt"><privateKey></span>$PATH_TO_PRIVATE_KEY<span class="nt"></privateKey></span>
+ <span class="nt"><passphrase></span>$SSH_PASSPHRASE<span class="nt"></passphrase></span>
+ <span class="nt"><directoryPermissions></span>775<span class="nt"></directoryPermissions></span>
+ <span class="nt"><filePermissions></span>644<span class="nt"></filePermissions></span>
+ <span class="c"><!-- following is only for Windows only</span>
+<span class="c"> <configuration></span>
+<span class="c"> <sshExecutable>plink</sshExecutable></span>
+<span class="c"> <scpExecutable>pscp</scpExecutable></span>
+<span class="c"> <scpArgs>-2Bp</scpArgs></span>
+<span class="c"> <sshArgs>-2</sshArgs></span>
+<span class="c"> </configuration></span>
+<span class="c"> --></span>
+ <span class="nt"></server></span>
+ <span class="c"><!-- ASF Nexus settings --></span>
+ <span class="nt"><server></span>
+ <span class="nt"><id></span>apache.snapshots.https<span class="nt"></id></span>
+ <span class="nt"><username></span>$USERNAME<span class="nt"></username></span>
+ <span class="nt"><password></span>$APACHE_LDAP_PWD<span class="nt"></password></span>
+ <span class="nt"></server></span>
+ <span class="nt"><server></span>
+ <span class="nt"><id></span>apache.releases.https<span class="nt"></id></span>
+ <span class="nt"><username></span>$USERNAME<span class="nt"></username></span>
+ <span class="nt"><password></span>$APACHE_LDAP_PWD<span class="nt"></password></span>
+ <span class="nt"></server></span>
+ <span class="nt"></servers></span>
+<span class="nt"></settings></span>
+</pre></div>
+
+
+<p>Notes:</p>
+<ul>
+<li><em><code>$USERNAME</code> is the remote username on <code>people.apache.org</code>,
+ not necessarily your local userid.</em></li>
+<li><em><code>$PATH_TO_PRIVATE_KEY</code> is the path to the private <code>ssh</code> key generated, e.g.
+<code>/home/yourLocalUserId/.ssh/id_dsa</code>. For cygwin users,
+you will need to enter the full cygwin path:
+<code>/cygdrive/c/cygwin/home/yourLocalUserId/.ssh/id_dsa</code>.</em></li>
+<li><em><code>$SSH_PASSPHRASE</code> for the supplied <code>$PATH_TO_PRIVATE_KEY</code>. If you
+don't use this in your <code>settings.xml</code> file, then you will be prompted for it
+during the Release processing.</em></li>
+<li><em><code>$APACHE_LDAP_PWD</code> is your Apache LDAP password, which is shared
+between SVN and password login for <code>people.apache.org</code>.</em></li>
+</ul></div>
+ <!-- Content -->
+ </td>
+ </tr>
+ </table>
+ </td>
+ <td id="cell-2-2" colspan="2"> </td>
+ </tr>
+ <tr width="100%">
+ <td id="cell-3-0"> </td>
+ <td id="cell-3-1"> </td>
+ <td id="cell-3-2">
+ <div id="footer">
+ <!-- Footer -->
+ <div id="site-footer">
+ </div>
+ <!-- Footer -->
+ </div>
+ </td>
+ <td id="cell-3-3"> </td>
+ <td id="cell-3-4"> </td>
+ </tr>
+ <tr width="100%">
+ <td id="cell-4-0" colspan="2"> </td>
+ <td id="cell-4-1">
+ <div id="footer-legal">
+Copyright (C) 2010-2012 The Apache Software Foundation. Licensed under <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License 2.0</a>.<br />
+Apache and the Apache feather logo are trademarks of The Apache Software Foundation.<br />
+Other names may be trademarks of their respective owners.
+ </div>
+ </td>
+ <td id="cell-4-2" colspan="2"> </td>
+ </tr>
+ <tr width="100%">
+ <td id="cell-4-0" colspan="2"> </td>
+ <td id="cell-4-1"> </td>
+ <td id="cell-4-2" colspan="2"> </td>
+ </tr>
+</table>
+</body>
+</html>
Added: websites/staging/bval/trunk/content/resources/blog.js
==============================================================================
--- websites/staging/bval/trunk/content/resources/blog.js (added)
+++ websites/staging/bval/trunk/content/resources/blog.js Sat Mar 10 22:51:09 2012
@@ -0,0 +1,29 @@
+function getBlogEntries(root, space, limit, prototype, targetContainer) {
+ $.getJSON(
+ root + "/rest/prototype/1/search.json?type=blogpost&spaceKey=" + space,
+ function(data) {
+ var successCount;
+ for (var i = 0; i < data.result.length && successCount < limit; i++) {
+ entry = data.result[i];
+ var detailLink = result[i].link.filter(function(element, index, array) {
+ return element.rel == "self";
+ });
+ if (detailLink) {
+ successCount++;
+ item = $(prototype).clone();
+ $.getJSON(detailLink.href, function(data) {
+ $(".detail", item).text(data.body);
+ });
+
+ $(".date", item).text(entry.createdDate.friendly);
+ $(".title", item).text(entry.title);
+ $(item).show();
+ $(item).appendTo(targetContainer);
+ }
+ }
+ if (successCount > 0) {
+ $(targetContainer).show();
+ }
+ }
+ );
+}
Added: websites/staging/bval/trunk/content/resources/code.css
==============================================================================
--- websites/staging/bval/trunk/content/resources/code.css (added)
+++ websites/staging/bval/trunk/content/resources/code.css Sat Mar 10 22:51:09 2012
@@ -0,0 +1,64 @@
+.codehilite .hll { background-color: #ffffcc }
+.codehilite { background: #f0f0f0; }
+.codehilite .c { color: #60a0b0; font-style: italic } /* Comment */
+.codehilite .err { border: 1px solid #FF0000 } /* Error */
+.codehilite .k { color: #007020; font-weight: bold } /* Keyword */
+.codehilite .o { color: #666666 } /* Operator */
+.codehilite .cm { color: #60a0b0; font-style: italic } /* Comment.Multiline */
+.codehilite .cp { color: #007020 } /* Comment.Preproc */
+.codehilite .c1 { color: #60a0b0; font-style: italic } /* Comment.Single */
+.codehilite .cs { color: #60a0b0; background-color: #fff0f0 } /* Comment.Special */
+.codehilite .gd { color: #A00000 } /* Generic.Deleted */
+.codehilite .ge { font-style: italic } /* Generic.Emph */
+.codehilite .gr { color: #FF0000 } /* Generic.Error */
+.codehilite .gh { color: #000080; font-weight: bold } /* Generic.Heading */
+.codehilite .gi { color: #00A000 } /* Generic.Inserted */
+.codehilite .go { color: #808080 } /* Generic.Output */
+.codehilite .gp { color: #c65d09; font-weight: bold } /* Generic.Prompt */
+.codehilite .gs { font-weight: bold } /* Generic.Strong */
+.codehilite .gu { color: #800080; font-weight: bold } /* Generic.Subheading */
+.codehilite .gt { color: #0040D0 } /* Generic.Traceback */
+.codehilite .kc { color: #007020; font-weight: bold } /* Keyword.Constant */
+.codehilite .kd { color: #007020; font-weight: bold } /* Keyword.Declaration */
+.codehilite .kn { color: #007020; font-weight: bold } /* Keyword.Namespace */
+.codehilite .kp { color: #007020 } /* Keyword.Pseudo */
+.codehilite .kr { color: #007020; font-weight: bold } /* Keyword.Reserved */
+.codehilite .kt { color: #902000 } /* Keyword.Type */
+.codehilite .m { color: #40a070 } /* Literal.Number */
+.codehilite .s { color: #4070a0 } /* Literal.String */
+.codehilite .na { color: #4070a0 } /* Name.Attribute */
+.codehilite .nb { color: #007020 } /* Name.Builtin */
+.codehilite .nc { color: #0e84b5; font-weight: bold } /* Name.Class */
+.codehilite .no { color: #60add5 } /* Name.Constant */
+.codehilite .nd { color: #555555; font-weight: bold } /* Name.Decorator */
+.codehilite .ni { color: #d55537; font-weight: bold } /* Name.Entity */
+.codehilite .ne { color: #007020 } /* Name.Exception */
+.codehilite .nf { color: #06287e } /* Name.Function */
+.codehilite .nl { color: #002070; font-weight: bold } /* Name.Label */
+.codehilite .nn { color: #0e84b5; font-weight: bold } /* Name.Namespace */
+.codehilite .nt { color: #062873; font-weight: bold } /* Name.Tag */
+.codehilite .nv { color: #bb60d5 } /* Name.Variable */
+.codehilite .ow { color: #007020; font-weight: bold } /* Operator.Word */
+.codehilite .w { color: #bbbbbb } /* Text.Whitespace */
+.codehilite .mf { color: #40a070 } /* Literal.Number.Float */
+.codehilite .mh { color: #40a070 } /* Literal.Number.Hex */
+.codehilite .mi { color: #40a070 } /* Literal.Number.Integer */
+.codehilite .mo { color: #40a070 } /* Literal.Number.Oct */
+.codehilite .sb { color: #4070a0 } /* Literal.String.Backtick */
+.codehilite .sc { color: #4070a0 } /* Literal.String.Char */
+.codehilite .sd { color: #4070a0; font-style: italic } /* Literal.String.Doc */
+.codehilite .s2 { color: #4070a0 } /* Literal.String.Double */
+.codehilite .se { color: #4070a0; font-weight: bold } /* Literal.String.Escape */
+.codehilite .sh { color: #4070a0 } /* Literal.String.Heredoc */
+.codehilite .si { color: #70a0d0; font-style: italic } /* Literal.String.Interpol */
+.codehilite .sx { color: #c65d09 } /* Literal.String.Other */
+.codehilite .sr { color: #235388 } /* Literal.String.Regex */
+.codehilite .s1 { color: #4070a0 } /* Literal.String.Single */
+.codehilite .ss { color: #517918 } /* Literal.String.Symbol */
+.codehilite .bp { color: #007020 } /* Name.Builtin.Pseudo */
+.codehilite .vc { color: #bb60d5 } /* Name.Variable.Class */
+.codehilite .vg { color: #bb60d5 } /* Name.Variable.Global */
+.codehilite .vi { color: #bb60d5 } /* Name.Variable.Instance */
+.codehilite .il { color: #40a070 } /* Literal.Number.Integer.Long */
+div .codehilite { overflow: inherit }
+div .codehilite pre { white-space: pre-wrap; overflow: inherit }