Bug 49281 - Release version 1.0
Summary: Release version 1.0
Status: CLOSED FIXED
Alias: None
Product: Fop - Now in Jira
Classification: Unclassified
Component: general (show other bugs)
Version: trunk
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: fop-dev
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-12 15:08 UTC by Simon Pepping
Modified: 2012-04-06 21:52 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Simon Pepping 2010-05-12 15:08:42 UTC
Release version 1.0

Step 1: List all bugs that must be solved before a release can take place
(release critical bugs). Make this bug depend on each release critical bug and
write a short argument why the bug is release critical.

Steps 2ff: See web site.
Comment 1 Simon Pepping 2010-07-02 08:56:53 UTC
Step 2: Before the release

# Determine whether this is a Release Candidate or a Release.
# Determine whether further testing is required.
# Commit any outstanding changes
Comment 2 Simon Pepping 2010-07-02 09:02:43 UTC
Step 3: Preparing the release

# Create a branch called branches/fop-v_vv
# Edit release notes (README and status.xml in the root).
# Update the index.xml, site.xml and download.xml for the new version.
# Update the version numbers in the release column on the compliance page (compliance.xml); update the compliance in the release column to the current state (development column).
# Update version number in build.xml (not to be merged back into trunk).
# Copy trunk documentation directory to a new directory with the version number, and update any links and the .htaccess file for redirections.
# Copy test/fotree/disabled-testcases.xml and test/layoutengine/disabled-testcases.xml to the new version directory <version>/fotree/disabled-testcases.xml and <version>/layoutengine/disabled-testcases.xml. Copy known-issues.xml to the new version directory. Copy knownissues-overview.xml from the previous to the new version directory.
# Delete the previous version directory.
# Build the dist files (build[.sh] dist) and upload them to your web directory on people.apache.org
# Ask on fop-dev to check the branch and the generated dist files for errors.
# Tag the source tree with the release ID. For example, if the release is 1.0: svn copy https://svn.apache.org/repos/asf/xmlgraphics/fop/branches/fop-1_0 https://svn.apache.org/repos/asf/xmlgraphics/fop/tags/fop-1_0
# Make a fresh checkout with the just created tag: svn co https://svn.apache.org/repos/asf/xmlgraphics/fop/tags/fop-1_0
# Copy the hyphenation patterns jar file fop-hyph.jar to lib/ (e.g. from http://sourceforge.net/projects/offo
# Alternatively, create a build-local.properties file that points to the above libs.
# Run build[.sh] dist. Do this using Sun JDK 1.4.2_08 or later. A Forrest installation is needed.
# Create signatures. Don't forget to upload your KEY: gpg -a -b --force-v3-sigs fop-1.0-src.tar.gz etc.
# Upload the dist and signature files to your web directory on people.apache.org (An account on minotaur is needed): scp fop-1.0*.tar.gz* <your name>@people.apache.org:public_html/ etc.
# Check permissions: chmod 664 ... ; chgrp xmlgraphics ...
# Add MD5 sums: md5 fop-1.0-src.tar.gz > fop-1.0-src.tar.gz.md5 etc.
# Make a test download.
# Start a vote for the release on general@xmlgraphics.a.o. The message should point to the release files and list the MD5 sums (cat *.md5). The vote is open for 72hrs.
Comment 3 Simon Pepping 2010-07-02 09:04:21 UTC
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.
Comment 4 Simon Pepping 2010-07-23 02:51:01 UTC
Almost completed. Left to be done: deploy the maven bundle. I have no
experience with Maven and I do not have it installed, so I cannot do this task.
Comment 5 Glenn Adams 2012-03-28 06:27:27 UTC
this is good process information that should be exported into the FOP Dev docs or FOP Wiki
Comment 6 Glenn Adams 2012-04-06 21:52:04 UTC
update release checklist in site docs at:  http://xmlgraphics.apache.org/fop/dev/release.html

see http://svn.apache.org/viewvc?view=revision&revision=1310603