Author: tandraschko
Date: Mon Nov 12 14:59:45 2018
New Revision: 1846427

URL: http://svn.apache.org/viewvc?rev=1846427&view=rev
Log:
CMS commit to openwebbeans by tandraschko

Modified:
    openwebbeans/cms-site/trunk/content/release-checklist.mdtext

Modified: openwebbeans/cms-site/trunk/content/release-checklist.mdtext
URL: 
http://svn.apache.org/viewvc/openwebbeans/cms-site/trunk/content/release-checklist.mdtext?rev=1846427&r1=1846426&r2=1846427&view=diff
==============================================================================
--- openwebbeans/cms-site/trunk/content/release-checklist.mdtext (original)
+++ openwebbeans/cms-site/trunk/content/release-checklist.mdtext Mon Nov 12 
14:59:45 2018
@@ -21,22 +21,22 @@ Notice:    Licensed to the Apache Softwa
 Before performing the release you need to configure your environment if you 
haven't done it before.
 
  1. Publishing Maven Artifacts 
(http://www.apache.org/dev/publishing-maven-artifacts.html)
- 2. Go to the section SETUP YOUR DEVELOPMENT ENVIRONMENT and generate the pgp 
key signature. Don't forget to distribute the public key step.
+ 2. Go to the section SETUP YOUR DEVELOPMENT ENVIRONMENT and generate the pgp 
key signature. Don't forget to distribute the public key step.  
     Generate PGP signature: 
https://blog.sonatype.com/2010/01/how-to-generate-pgp-signatures-with-maven/#.Vm9Km8q22-q
-
+    
 ## Prepare
 
  1. JIRA Release Management
        - Find resolved issues and close them
        - Create ${version.next} (if not already done)
        - Move unresolved issues from ${version} (2.0.8) to ${version.next} 
(2.0.9)  
-
+  
 
  2. Update README
        - Export changelog from JIRA
        - add it to readme/README.txt
        - also update the version numbers in the preface  
-
+  
 
  3. Release via MVN
        - mvn clean install -Papache-release
@@ -48,13 +48,13 @@ Before performing the release you need t
        can you deploy the tag the manually to nexus  
        - commit the version change in trunk
        - checkout the tag and execute: mvn clean install deploy 
-Papache-release  
-
+  
 
  4. Provide the staging repository 
        - login to nexus: https://repository.apache.org/#stagingRepositories
        - select the staging repository and "close" it
        - the final url should be similar to 
https://repository.apache.org/content/repositories/orgapacheopenwebbeans-1047  
-
+  
 
  5. Provide assembly
        - SVN https://dist.apache.org/repos/dist/dev/openwebbeans/
@@ -68,10 +68,10 @@ Before performing the release you need t
                - openwebbeans-distribution-2.0.8-binary.zip
                - openwebbeans-distribution-2.0.8-binary.zip.asc
                - openwebbeans-distribution-2.0.8-binary.zip.sha512 (must be 
generated manually)  
-
+  
 
  6. Send the VOTE mail  
-
+  
 
 ## After successful vote 
 
@@ -79,39 +79,39 @@ Before performing the release you need t
        - login to nexus: https://repository.apache.org/#stagingRepositories
        - select the staging repository and "release" it
        - the artifacts will be synced with the maven repos now  
-
+  
 
  2. JIRA Release Management
        - Select the version and release it  
-
+  
 
  3. Upload assembly
        - SVN https://dist.apache.org/repos/dist/release/openwebbeans/
        - commit same files as in 5) under the new directory ${version} (2.0.8)
        - delete ${version.old} (2.0.7) directory  
-
+  
 
  4. Apache Reporter Service
        - Wait for the mail
        - login to https://reporter.apache.org/addrelease.html?openwebbeans
        - add the ${version} and release date  
-
+  
 
 ## After the artifacts has been synced to central maven repo
 
  1. Create blog
        - Login to https://blogs.apache.org/owb/
        - Add a post for the new release, this will automatically picked up by 
the Site  
-
+  
 
  2. Update Site
        - Login to 
https://cms.apache.org/redirect?uri=http://openwebbeans.apache.org/
        - Edit news.mdtext
        - Edit download.mdtext
        - Publish via https://cms.apache.org/openwebbeans/publish  
-
+  
 
  3. Send release mail  
-
+  
 
  4. Twitter  
\ No newline at end of file


Reply via email to