ws-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <>
Subject [Ws Wiki] Update of "FrontPage/Woden/WodenReleaseGuide" by sagara
Date Mon, 07 Dec 2009 15:54:58 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Ws Wiki" for change notification.

The "FrontPage/Woden/WodenReleaseGuide" page has been changed by sagara.


  = Woden Release Guide =
+ The Woden release process involves many steps and checks. To keep compliant with Apache
process requirements            of WS it is important that it is followed.
+  1. Build and test the current Woden release candidate. The 'dist" Maven profile is used
to create the binary and source archives  (.zip, .tar.gz, .tar.bz2) and the hash digests 
                 (md5, sha1) for each archive file. Use foolowing maven coomand to create
above artifacts.                                                                         
   <<BR>>'''mvn clean package assembly:assembly  antrun:run  -P dist         
+  1. Sign the binary and source archives, which will create a .asc signature file for each
archive file.<<BR>>                    <<BR>>                    
    e.g.<<BR>>                       gpg --armor --output
--detach-sig <<BR>>                      gpg --verify <<BR>>                    <<BR>>
+  1. Upload the binary and source archives and their hash digests and signature files to
               into some directory path under your public_html
directory so that you can include a                   link to the files in the [VOTE] request
email. Also upload the KEYS file and release-notes.html                         from [woden
root] and junit-noframes.html from the [woden root]/build/test-results/html directory.   
                  Make sure you chmod the file permissions so others can read them (e.g. 744).<<BR>>
                      <<BR>>                         e.g.<<BR>>  
                    [jkaputin home]/public_html/woden/milestones/1.0M9 <<BR>>
        accessible at url...<<BR>>                         [[|]]
<<BR>>                   <<BR>>
+  1. Check that you can download/unzip the files.<<BR>>                  Create
hash digests of the downloaded archives and check them against the downloaded hash files.<<BR>>
                  <<BR>>                         e.g.<<BR>>      
                $ dir <<BR>>          
<<BR>>                       $ cat <<BR>>
                    3009d6f6fea14b7536c22028944bb03a <<BR>>                  
      $ md5sum <<BR>>                      3009d6f6fea14b7536c22028944bb03a
* <<BR>>                    <<BR>>
+  1. Post a vote request email to woden-dev asking devs to vote on the proposed M7b release.
                    Post the voting results.<<BR>>                  When posting
a vote request to any mailing list, start the subject line with the eye-catcher [VOTE]. <<BR>>
+  1. If woden-dev vote successful, post to asking the WSPMC to approve
a Woden                     release. Post the voting results.<<BR>>          
              When posting a vote request to any mailing list, start the subject line with
the eye-catcher [VOTE]. <<BR>>                    <<BR>>
+  1. If WSPMC vote successful, move all the release files from your public_html directory
to the Woden                    file space on<<BR>>       
           <<BR>>                          cd /www/
<<BR>>                          cd milestones <<BR>>             
     Create a new directory for the release (e.g. /1.0M9)<<BR>>              
   Move the release files to this new directory.<<BR>>                     Copy
the file release-notes.html to a new file called README.html in this new directory       
                 (this will ensure the release notes are displayed after the list of files,
when this                    directory is accessed via the web).<<BR>>       
                <<BR>>                         e.g.<<BR>>        
              /www/ <<BR>>   
                   ...will be accessible via url...<<BR>>                  [[|]]
<<BR>>                    <<BR>>
+  1. Once again, check that:
+   * the file permissions are set correctly
+   * you can download/unzip the files
+   * the downloaded hash digests are correct  <<BR>>                    <<BR>>
+  1. Update the Woden web site (add the release download to the Builds page and add a News
item                          announcing the release to the Woden home page). <<BR>>
+  1. Post a release announcement to woden-dev, general@ws. <<BR>>           
+  1. Final step, which Axis2 folks will do, it to upload Woden release binary jar to a maven
                    repository...I think Dims can upload to ws.zones. <<BR>> 
+ Some example mailing list posts for reference:
+ [[<>|[VOTE]
woden-dev and WSPMC]]
+ [[<>|[RESULT]]]
+ [[<>|[VOTE]
+ [[<>|[ANNOUNCE]]]

View raw message