svn commit: r1713908 - /felix/site/trunk/content/documentation/development/release-management-nexus.mdtext

[bi...@apache.org]

Author: bimargulies
Date: Wed Nov 11 18:33:50 2015
New Revision: 1713908

URL: http://svn.apache.org/viewvc?rev=1713908&view=rev
Log:
finish previous task.

Modified:
    felix/site/trunk/content/documentation/development/release-management-nexus.mdtext

Modified: felix/site/trunk/content/documentation/development/release-management-nexus.mdtext
URL: http://svn.apache.org/viewvc/felix/site/trunk/content/documentation/development/release-management-nexus.mdtext?rev=1713908&r1=1713907&r2=1713908&view=diff
==============================================================================
--- felix/site/trunk/content/documentation/development/release-management-nexus.mdtext (original)
+++ felix/site/trunk/content/documentation/development/release-management-nexus.mdtext Wed Nov 11 18:33:50 2015
@@ -1,4 +1,4 @@
-Title: Release Management (Nexus)
+Title: Release Management
 
 *This is the new release process for Apache Felix, based on the updated Maven [process](http://maven.apache.org/developers/release/releasing.html)*
 
@@ -96,7 +96,15 @@ the released version.
     * login to [https://repository.apache.org](https://repository.apache.org) using your Apache SVN credentials. Click on *Staging* on the left. Then click on *org.apache.felix* in the list of repositories. In the panel below you should see an open repository that is linked to your username and IP. Right click on this repository and select *Close*. This will close the repository from future deployments and make it available for others to view. If you are staging multiple releases together, skip this step until you have staged everything
 1. Verify the staged artifacts
     * if you click on your repository, a tree view will appear below. You can then browse the contents to ensure the artifacts are as you expect them. Pay particular attention to the existence of \*.asc (signature) files. If you don't like the content of the repository, right click your repository and choose *Drop*. You can then rollback your release (see *Canceling the Release*) and repeat the process
-    * note the staging repository URL (especially the number at the end of the URL) you will need this in your vote email
+    * note the staging repository URL (especially the number at the end of the URL) you will need this in your vote email.
+
+## Stage the generated documentation
+
+(This only applies to the maven-bundle-plugin so far.)
+
+Run:
+
+    $ mvn site:site site:stage scm-publish:publish-scm
 
 ## Starting the Vote
 
@@ -262,6 +270,16 @@ For the last two tasks, it's better to g
 
 Go to [Admin](https://issues.apache.org/jira/secure/project/ViewProject.jspa?pid=12310100) section on the FELIX JIRA and mark the Y.Z version as released - create version Y.Z+1, if that hasn't already been done.
 
+## Publish Generated Documentation
+
+This procedure applies to the maven-bundle-plugin; it may expand to others. The bundle plugin's maven-site-plugin doc is published to SVN by the
+maven-scm-publish plugin at the location
+https://svn.apache.org/repos/infra/websites/production/felix/content/components/bundle-plugin-archives/bundle-plugin-LATEST. At release time, you
+rename that from LATEST to the correct version, and then copy it to https://svn.apache.org/repos/infra/websites/production/felix/content/components/bundle-plugin.
+
+See [some doc from the Maven project](http://maven.apache.org/developers/website/deploy-component-reference-documentation.html#Publishing_versioned_component_reference_documentation).
+
+
 ## Create an Announcement
 
 
@@ -343,4 +361,4 @@ When running the `mvn release:prepare` c
     svn: Commit failed (details follow):
     svn: MKACTIVITY of '/repos/asf/!svn/act/4f11ad5d-9161-0410-b4dd-cb727141ea8c': authorization failed (https://svn.apache.org){code}
     
-This is due to a bug in Subversion on the Mac, as described by Brett Porter in his [blog|http://blogs.exist.com/bporter/2008/02/25/working-around-non-interactive-problems-in-leopards-subversion/]. He proposes putting an "svn" script at the head of your path to fix the issue.
+This is due to a bug in Subversion on the Mac, as described by Brett Porter in his [blog|http://blogs.exist.com/bporter/2008/02/25/working-around-non-interactive-problems-in-leopards-subversion/]. He proposes putting an "svn" script at the head of your path to fix the issue.
\ No newline at end of file