bugzilla | 2 Jul 15:02 2010

DO NOT REPLY [Bug 49281] Release version 1.0


--- Comment #2 from Simon Pepping <spepping <at> apache.org> 2010-07-02 09:02:43 EDT ---
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
# Make a fresh checkout with the just created tag: svn co
# Copy the hyphenation patterns jar file fop-hyph.jar to lib/ (e.g. from
(Continue reading)