Author: buildbot
Date: Mon Aug 12 09:41:53 2019
New Revision: 1048512
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 Mon Aug 12 09:41:53 2019
@@ -1 +1 @@
-1861597
+1864952
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 Mon Aug 12
09:41:53 2019
@@ -144,7 +144,7 @@ artifacts and using Nexus can be found o
<p>Environment setup for releasing artifacts (same for <code>SNAPSHOT</code>s
and
releases)</p>
<ol>
-<li>Use the latest Oracle 8 JDK</li>
+<li>Use the latest Oracle 8 JDK (with javafx, it's required by the TCK!)</li>
<li>Use Maven 3.2.1 or later</li>
<li>Make sure the <a href="/release-setup.html">Release Setup</a> steps have
been performed.</li>
</ol>
@@ -160,7 +160,7 @@ releases)</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>Commit any changes back to svn:<div class="codehilite"><pre>svn commit -m
<span class="s2">"updating files for release"</span>
+<li>Commit any changes back to GIT:<div class="codehilite"><pre>git commit -a
-m <span class="s2">"updating files for release"</span> & git push
</pre></div>
@@ -186,14 +186,14 @@ releases)</p>
<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>
+<li>All jars/zips/poms have <code>.asc</code> (PGP signature) files</li>
</ol>
</li>
</ol>
</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
+ The dry run will not commit any changes back to GIT 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>
@@ -227,13 +227,13 @@ What is the new development version for
<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
+ changes that would have been committed to GIT. 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>
+<div class="codehilite"><pre>git commit -a -m <span class="s2">"fixing
formatting for release"</span> & git push
</pre></div>
@@ -248,7 +248,7 @@ the next version.</li>
<li><a href="#ReleaseProcess-Verifyingreleasesignatures">Verify
signatures</a></li>
</ol>
</li>
-<li>Once any failures or required updates have been committed to svn,
+<li>Once any failures or required updates have been committed to GIT,
rollback the release prepare files:<div class="codehilite"><pre>mvn
-Papache-release release:rollback
</pre></div>
@@ -332,7 +332,7 @@ Subject: [VOTE] Apache BVal <version&
I've created a <version> release candidate, with the following
artifacts up for a vote:
Git source tag:
-https://svn.apache.org/repos/asf/bval/tags/<version>/
+https://gitbox.apache.org/repos/asf?p=bval.git;a=tags
Maven staging repo:
https://repository.apache.org/content/repositories/orgapachebval-020/
@@ -360,13 +360,13 @@ The vote will be open for at least 72 ho
<div class="codehilite"><pre>To: [email protected]
Subject: [DISCUSS] Apache BVal <version> Release Candidate
-Discussion thread for vote on <version> release candidate, with SVN
source tag (r9999999).
+Discussion thread for vote on <version> release candidate, with GIT
source tag (r9999999).
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
+- can you build the contents of source-release.zip and GIT tag
- do all of the staged jars/zips contain the required LICENSE and NOTICE 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
(i.e. http://www.apache.org/dist/bval/)
