Author: buildbot
Date: Thu Oct 18 16:37:37 2018
New Revision: 1036384
Log:
Staging update by buildbot for bval
Modified:
websites/staging/bval/trunk/content/ (props changed)
websites/staging/bval/trunk/content/release-process.html
Propchange: websites/staging/bval/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Oct 18 16:37:37 2018
@@ -1 +1 @@
-1844122
+1844261
Modified: websites/staging/bval/trunk/content/release-process.html
==============================================================================
--- websites/staging/bval/trunk/content/release-process.html (original)
+++ websites/staging/bval/trunk/content/release-process.html Thu Oct 18
16:37:37 2018
@@ -180,9 +180,8 @@ releases)</p>
</li>
<li>
-<p>Run the <a href="/beanvalidation-tck.html">Bean Validation TCK</a> to
verify the latest code passes.</p>
-</li>
-<li>Inspect the files in your local target directories to ensure:<ol>
+<p>Inspect the files in your local target directories to ensure:</p>
+<ol>
<li>All jars and zips include <code>LICENSE</code> and <code>NOTICE</code>
files</li>
<li>The NOTICE files cover all third-party included files (like XSD
schemas)</li>
@@ -193,29 +192,6 @@ schemas)</li>
</ol>
</li>
<li>
-<p>For new major releases (like 1.0.0 to 1.1.0)</p>
-<ol>
-<li>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:<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.
@@ -270,7 +246,6 @@ validation you feel necessary. The follo
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>Once any failures or required updates have been committed to svn,
@@ -321,11 +296,10 @@ tar -czf 1.0-rc1.tar.gz 1.0-rc1/
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>
+</li>
+<li>
+<p>Verify the release artifacts:</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>
@@ -360,7 +334,7 @@ Subject: [VOTE] Apache BVal <version&
I've created a <version> release candidate, with the following
artifacts up for a vote:
-SVN source tag (r9999999):
+Git source tag (r9999999):
https://svn.apache.org/repos/asf/bval/tags/<version>/
Maven staging repo:
@@ -369,8 +343,8 @@ https://repository.apache.org/content/re
Source release:
https://repository.apache.org/content/repositories/orgapachebval-020/org/apache/bval/bval-parent/<version>/bval-parent-<version>-source-release.zip
-Staging site:
-http://people.apache.org/~mbenson/bval/<version>/staging-site/
+Site:
+https://dist.apache.org/repos/dist/dev/bval/2.0.0-RC1/site/index.html
PGP release keys (signed using 2163DDCE):
http://www.apache.org/dist/bval/KEYS
