You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@bval.apache.org by ta...@apache.org on 2019/08/12 10:08:34 UTC

svn commit: r1864956 - /bval/cms-site/trunk/content/release-process.mdtext

Author: tandraschko
Date: Mon Aug 12 10:08:34 2019
New Revision: 1864956

URL: http://svn.apache.org/viewvc?rev=1864956&view=rev
Log:
minor changes

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=1864956&r1=1864955&r2=1864956&view=diff
==============================================================================
--- bval/cms-site/trunk/content/release-process.mdtext (original)
+++ bval/cms-site/trunk/content/release-process.mdtext Mon Aug 12 10:08:34 2019
@@ -125,21 +125,20 @@ need to rollback the release after the n
 1. Verify the release artifacts:
     1. Verify the staged artifacts in the nexus repo:
         1. [https://repository.apache.org/index.html](https://repository.apache.org/index.html)
-        1. **Enterprise --> Staging**
-        1. **Staging tab --> Name column --> org.apache.bval**
+        1. **Build Promotion --> Staging Repositories**
         1. Navigate through the artifact tree and make sure that all binary, `javadoc`,
          `sources`, and `tests` jars, as well as `pom`s, ... have `.asc` (GPG signature) and `.md5`
          files (see [Repository FAQ][] and [Detached Signatures][]). The `source-release.zip` of `bval-parent`
          should likewise have signature and checksum files.
-    1. Upload the source artifacts to the dev dist area at
-         `https://dist.apache.org/repos/dist/dev/bval/source`.
+    1. Upload the source artifacts to the dev dist area via SVN at
+         `https://dist.apache.org/repos/dist/dev/bval/source`
+         (./target/bval-parent-<version>-source-release.zip and the .asc + .sha512 file)
     1. Check out the newly created tag and build the site using `mvn post-site`.
     1. Verify the HTML links in `target/staging/index.html` are correct
     1. Commit the contents of `target/staging` to `https://dist.apache.org/repos/dist/dev/bval/<version-RCn>/site/`
     1. Close the nexus staging repo:
         1. [https://repository.apache.org/index.html](https://repository.apache.org/index.html)
-        1. **Enterprise --> Staging**
-        1. **Staging tab --> Name column --> org.apache.bval**
+        1. **Build Promotion --> Staging Repositories**
         1. Click the checkbox to select the open `org.apache.bval-XXX` staging repo,
          then click the **Close** button on the toolbar above.
 
@@ -205,8 +204,7 @@ received (see [Recovering from a vetoed
 1. Finalizing a release
     1. Promote the staged nexus artifacts:
         1. [https://repository.apache.org/index.html](https://repository.apache.org/index.html)
-        1. **Enterprise --> Staging**
-        1. **Staging tab --> Name column --> org.apache.bval**
+        1. **Build Promotion --> Staging Repositories**
         1. Right click on the closed `org.apache.bval-XXX` staging repo and select **Release**.
 
     1. Update the generated portion of the website: