|
Size: 2895
Comment:
|
← Revision 6 as of 2009-09-20 22:48:13 ⇥
Size: 2895
Comment: converted to 1.6 markup
|
| No differences found! | |
Relase Plan Axis2 0.9
New release completes the most of the functionalities targeted by Axis2, the remaining functionalites are added as Jira issues. This Relase added
- Data Binding
- MTOM
- Module Architecture
- SOAP 1.2 support
- WSA Submission Final
- REST support
With most updates to the Archtecutre.
Source level TODOs for relase
- Update the User guide for the Data binding
- SWA Documents
- Update REST documents
- Updates the TCP documents
- MTOM Documents
Axis2 0.9 feature list
- SOAP 1.1/SOAP 1.2 support
- WSDL 1.1
- WSA Submission and Final
- Module Architecture
- Context Hierachy
- Transports SMTP
- Transport HTTP
- Transport TCP
- Raw XML Providers
- Support for MTOM/MIME/SwA
- Deployment
- Client API modules
- WSDL2Java
- Java2WSDL
- REST support
- XML Beans based data binding implemntation
Steps for Axis2 0.9 Release
Create a Key Pair
If you do not have one create a key pair
# gpg --gen-key
the keys will be genrated in the ~/.gnupg
Export the Keys
gpg --armor --export hemapani@gmail.com > KEYS
update KEYS
cd ~/release1-4-alpha cat KEYS >> /www/www.apache.org/dist/ws/axis2/KEYS
Cut the relase
- tag the SVN
Create Distribution
- Build Distribution Files
Take a new checkout and from the root direcotry
# maven clean #maven dist-bin # maven dist-src
This will create axis2-0.9-bin.zip axis2-0.9-src.zip files
Create Checksums (more info http://jakarta.apache.org/commons/releases/release.html)
Create Checksums
openssl md5 < axis2-0.9-bin.zip > axis2-0.9-bin.zip.md5
do same to axis2-0.9-src.zip
- Sign and verify the relases
#cd target/dist/
#gpg --armor --output axis2-0.9-bin.zip.asc --detach-sig axis2-0.9-bin.zip
#gpg --verify axis2-0.9-bin.zip.asc axis2-0.9-bin.zipdo same to axis2-0.9-src.zip
- Upload Releases and Move Releases Into Distribution Directories
- Update README,Check KEYS file, Update Symbolic Links,Remove symbolic links to current distributions, Update RELEASE-NOTES, Remove Obsolete Releases
- Deploy jar, project.xml and license.html to Java-Repository (maven repo) /www/www.apache.org/dist/axis2/jars
- Test Main Site Downloads
Web Site
- Update the website
- Test the Web Site
Releasing
- Create Announcements
- Update bugzilla
- Sent the Announcements There are some scripts available that help to automate some of these steps. In particular, see the following shell scripts in subversion under committers/tools/releases:
- sign_and_hash.sh (creates sigs and md5s)
- verify_sigs.sh (verifies sigs and checksums)
- symlinks.sh (creates symlinks)