https://issues.apache.org/bugzilla/show_bug.cgi?id=49280
--- Comment #3 from Simon Pepping <[email protected]> 2010-05-25 05:17:16 EDT --- Step 4: Releasing 4a. Make the Artifacts Available * Upload to people.apache.org. (An account on minotaur is needed): o scp xmlgraphics-commons-1.4-bin-* <you>@people.apache.org:/www/www.apache.org/dist/xmlgraphics/commons/binaries/ o scp xmlgraphics-commons-1.4-src.* <you>@people.apache.org:/www/www.apache.org/dist/xmlgraphics/commons/source/ * Check permissions: chmod 664 ... ; chgrp xmlgraphics ... * Make a test download. * Update HEADER.html and README.html in people.apache.org:/www/www.apache.org/dist/xmlgraphics/commons/ 4b. Make and release Maven Artifacts * Instructions on how to build the Maven artifacts for Commons, see Maven. 4c. Merge Back the Changes in the Trunk * svnmerge.py is your friend. Only the version number must not be merged back (that's why it's important to commit atomic changes). Note: Change from using svnmerge.py to svn 1.5's inbuilt merge support. * Put the exact release date in the website sources: status.xml and xdocs/news.xml * Update src/documentation/content/doap.rdf * Publish the website 4d. Post Announcements * Wait 24 hours (for the mirrors to catch up). * Post announcements on [email protected] and other related mailing lists. Note: Which? * Add the release version to the XMLGraphicsCommons Bugzilla component (just ask Christian as he has Bugzilla karma to do it) -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
