https://issues.apache.org/bugzilla/show_bug.cgi?id=49281
--- Comment #3 from Simon Pepping <spepp...@apache.org> 2010-07-02 09:04:21 EDT --- Step 4: After the release # When the release is accepted, copy the release files, their md5 sum files and the signature files to /www/www.apache.org/dist/xmlgraphics/fop/ in the subdirectories source and binaries. Create links to all files in the fop directory. Remove the links to the files of the previous version. # Update HEADER.html and README.html in people.apache.org:/www/www.apache.org/dist/xmlgraphics/fop/ # Wait 24 hours (for the mirrors to catch up). # Merge the changes of the subversion release branch back into trunk (not the version number in the build file) and delete the branch. # Deploy the updated documentation to the FOP website. # Post announcements on fop-dev and fop-user and other related mailing lists. # Ask a Bugzilla admin (Christian Geisert) to add a bugzilla entry for the new release id, or create an issue at https://issues.apache.org/jira/browse/INFRA. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
