velocity-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cbris...@apache.org
Subject svn commit: r1780324 - /velocity/site/cms/trunk/content/release-process.mdtext
Date Thu, 26 Jan 2017 03:27:59 GMT
Author: cbrisson
Date: Thu Jan 26 03:27:59 2017
New Revision: 1780324

URL: http://svn.apache.org/viewvc?rev=1780324&view=rev
Log:
[site] remove assembly + little fix

Modified:
    velocity/site/cms/trunk/content/release-process.mdtext

Modified: velocity/site/cms/trunk/content/release-process.mdtext
URL: http://svn.apache.org/viewvc/velocity/site/cms/trunk/content/release-process.mdtext?rev=1780324&r1=1780323&r2=1780324&view=diff
==============================================================================
--- velocity/site/cms/trunk/content/release-process.mdtext (original)
+++ velocity/site/cms/trunk/content/release-process.mdtext Thu Jan 26 03:27:59 2017
@@ -103,7 +103,7 @@ These steps must be performed **for each
     
         mvn release:prepare -Dusername=YOUR_SVN_USER -Dpassword=YOUR_SVN_PASSWORD
     
-    The plugin interactively will ask you the version to release, the Subversion tag to use
and the next snapshot version. It is reccomended to use the tag: `velocity-engine-parent-X.X.X`
(the default).
+    The plugin interactively will ask you the version to release, the Subversion tag to use
and the next snapshot version. Rather than `velocity-engine-parent-X.X` (the default), we
tend to use X.X for the tag name.
     
 * Perform the Release
     
@@ -141,29 +141,7 @@ These steps must be performed **for each
 	
     You can then rollback your release and repeat the process.
 
-    Note the repository URL, you will need this in your vote email.
-
-* Digest and upload assemblies
-
-    * Go into the release assembly target directory:
-        
-            cd target/checkout/assembly/target/assembly/out
-			
-        
-    * Create MD5 and SHA1 files for each files (including ASC files). You can do it with
this simple shell script:
-        
-            #!/bin/sh
-            
-            for fileitem in *
-            do
-              openssl md5 < $fileitem > $fileitem.md5
-              openssl sha1 < $fileitem > $fileitem.sha1
-            done
-        
-    * Upload everything to the build site:
-        
-            scp * user@people.apache.org:/www/people.apache.org/builds/velocity-engine-parent/${version}
-    
+    Note the repository URL, you will need this in your vote email.    
     
 * Release the JIRA version
     
@@ -246,16 +224,6 @@ These steps must be performed **for each
 	
 	Next click on "Repositories", select the "Releases" repository and validate that your artifacts
exist as you expect them.
     
-    * Move assemblies
-        
-        Move assemblies to the Apache distribution mirrors:
-        
-            ssh user@people.apache.org
-            
-            cd /www/people.apache.org/builds/velocity/${version}
-            mkdir /www/www.apache.org/dist/velocity/v${version}/
-            cp * /www/www.apache.org/dist/velocity/v${version}/
-        
     * Update the site
         
         Wait 24 hours to let the mirror sync to the release and then update the site. In
particular you have to update the index and the download pages:



Mime
View raw message