svn commit: r1612572 - /sling/site/trunk/content/documentation/development/release-management.mdtext

[cz...@apache.org]

Author: cziegeler
Date: Tue Jul 22 13:55:12 2014
New Revision: 1612572

URL: http://svn.apache.org/r1612572
Log:
CMS commit to sling by cziegeler

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

Modified: sling/site/trunk/content/documentation/development/release-management.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/development/release-management.mdtext?rev=1612572&r1=1612571&r2=1612572&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/development/release-management.mdtext (original)
+++ sling/site/trunk/content/documentation/development/release-management.mdtext Tue Jul 22 13:55:12 2014
@@ -287,13 +287,15 @@ To update the OBR you may use the Apache
     To deploy the project descriptor, checkout the tag of the bundle to deploy and run maven
 
         $ svn checkout http://svn.apache.org/repos/asf/sling/tags/the_module_tag
+        $ cd the_module_tag
         $ mvn clean install \
             org.apache.felix:maven-bundle-plugin:deploy \
             -DprefixUrl=http://repo1.maven.org/maven2 \
             -DremoteOBR=sling.xml \
-            -DaltDeploymentRepository=apache.releases::default::file:///path_to_site_checkout/obr
+            -DaltDeploymentRepository=apache.releases::default::file:///path_to_site_checkout/trunk/content/obr
 
     This generates the bundle descriptor and adds it to the sling.xml file of your site checkout.
+    As it also installs a fresh compiled version of the artifacts, it's better to remove that version from your local repository again (A new binary has new checksums etc.).
     
 2. Variant: Refer to Maven Repository
     
@@ -311,16 +313,14 @@ To update the OBR you may use the Apache
 
 3. Commit the Site Changes
 
-    In the Site checkout folder commit the changes to the `obr/sling.xml` files (you may also review the changes using the `svn diff` command).
+    In the Site checkout folder commit the changes to the `trunk/content/obr/sling.xml` files (you may also review the changes using the `svn diff` command).
     
-        $ svn commit -m"Add Bundle ABC Version X.Y.Z" obr/sling.xml
+        $ svn commit -m"Add Bundle ABC Version X.Y.Z" trunk/content/obr/sling.xml
 
-4. Update the Site on [people.apache.org](people.apache.org)
-    
-    After committing the changes, you have to update the site source, which is getting mirrored to the web servers on [people.apache.org](people.apache.org)
-    
-        $ ssh people.apache.org svn update /x1/www/sling.apache.org/obr/sling.xml
-
-    After updating the site source it will generally take an hour or two until the changes are visible on the web.
+4. Update the Site on 
 
+   Wait for the buildbot to update the staging area with your site update (see dev list for an email).
+   Then go to the CMS at https://cms.apache.org/redirect?uri=http://sling.apache.org/obr ,
+   update your checkout and then publish the site.
+    
 [1]: https://dist.apache.org/repos/dist/release/sling/