Author: mbenson
Date: Thu Oct 18 16:37:21 2018
New Revision: 1844261
URL: http://svn.apache.org/viewvc?rev=1844261&view=rev
Log:
CMS commit to bval by mbenson
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=1844261&r1=1844260&r2=1844261&view=diff
==============================================================================
--- bval/cms-site/trunk/content/release-process.mdtext (original)
+++ bval/cms-site/trunk/content/release-process.mdtext Thu Oct 18 16:37:21 2018
@@ -34,7 +34,6 @@ releases)
:::sh
mvn -Papache-release clean deploy
- 1. Run the [Bean Validation TCK](/beanvalidation-tck.html) to verify the
latest code passes.
1. Inspect the files in your local target directories to ensure:
1. All jars and zips include `LICENSE` and `NOTICE` files
1. The NOTICE files cover all third-party included files (like XSD
@@ -42,23 +41,6 @@ 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. For new major releases (like 1.0.0 to 1.1.0)
- 1. 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:
-
- :::sh
- mvn release:branch -DbranchName=1.0.x
-
-1. Checkout a clean copy of the trunk/branch to release using command line
-svn:
-
- :::sh
- svn checkout https://svn.apache.org/repos/asf/bval/trunk/ 1.0-rc1/
-
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
opportunity to verify that the release process will complete as expected.
@@ -103,7 +85,6 @@ 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. If you have access to the [JSR303 TCK](/jsr303-tck.html), run it.
1. Once any failures or required updates have been committed to svn,
rollback the release prepare files:
@@ -146,9 +127,6 @@ you'll have to also override the value p
site-deploy step to work. This is known to work for Linux, but not for Mac
and unknown for Windows.**
- 1. 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**.
1. Verify the release artifacts:
1. Verify the HTML links in staging-site/index.html are correct
1. Verify the staged artifacts in the nexus repo:
@@ -178,7 +156,7 @@ site:deploy` and will deploy the site fi
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:
@@ -187,8 +165,8 @@ site:deploy` and will deploy the site fi
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
