Author: tandraschko
Date: Mon Aug 12 09:41:45 2019
New Revision: 1864952
URL: http://svn.apache.org/viewvc?rev=1864952&view=rev
Log:
minor changes (git)
Modified:
bval/cms-site/trunk/content/release-process.mdtext
Modified: bval/cms-site/trunk/content/release-process.mdtext
URL:
http://svn.apache.org/viewvc/bval/cms-site/trunk/content/release-process.mdtext?rev=1864952&r1=1864951&r2=1864952&view=diff
==============================================================================
--- bval/cms-site/trunk/content/release-process.mdtext (original)
+++ bval/cms-site/trunk/content/release-process.mdtext Mon Aug 12 09:41:45 2019
@@ -10,7 +10,7 @@ artifacts and using Nexus can be found o
1. Environment setup for releasing artifacts (same for `SNAPSHOT`s and
releases)
- 1. Use the latest Oracle 8 JDK
+ 1. Use the latest Oracle 8 JDK (with javafx, it's required by the TCK!)
1. Use Maven 3.2.1 or later
1. Make sure the [Release Setup][] steps have been performed.
@@ -21,10 +21,10 @@ releases)
1. Update the text files in a working copy of the project root:
1. Update the `CHANGES.txt` based on the Text release reports from
JIRA.
1. Review and update `README.txt` if needed.
- 1. Commit any changes back to svn:
+ 1. Commit any changes back to GIT:
:::sh
- svn commit -m "updating files for release"
+ git commit -a -m "updating files for release" & git push
1. Stage any Roadmap or Release landing pages on the wiki.
1. Use `mvn apache-rat:check` to verify the source has the required
headers before
@@ -39,10 +39,10 @@ releases)
1. The NOTICE files cover all third-party included files (like XSD
schemas)
1. The `LICENSE` files include any third-party licenses (none at this
time)
- 1. All jars/zips/poms have `.asc` (PGP signature) and `.md5` files
+ 1. All jars/zips/poms have `.asc` (PGP signature) files
1. 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 :
1. Release version - take the default - (default 1.0)
@@ -70,14 +70,14 @@ you will be prompted for it:
1. Verify that the release process completed as expected:
1. The release plugin will create `pom.xml.tag` 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
`pom.xml.tag` and its corresponding `pom.xml` file should be the version
number.
1. If other formatting changes have been made you should review the changes
and then commit them:
:::sh
- svn commit -m "fixing formatting for release"
+ git commit -a -m "fixing formatting for release" & git push
1. Assuming the `.tag` files look OK you may proceed and do any other
validation you feel necessary. The following list may be helpful:
@@ -85,7 +85,7 @@ validation you feel necessary. The follo
right version. Sometimes the scm location can be the previous version not
the next version.
1. [Verify signatures](#ReleaseProcess-Verifyingreleasesignatures)
- 1. Once any failures or required updates have been committed to svn,
+ 1. Once any failures or required updates have been committed to GIT,
rollback the release prepare files:
:::sh
@@ -153,7 +153,7 @@ need to rollback the release after the n
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/
@@ -179,13 +179,13 @@ need to rollback the release after the n
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/)
