[FOray-commit] SF.net SVN: foray: [8258] trunk/foray/doc/web/dev/admin/release.html
Modular XSL-FO Implementation for Java.
Status: Alpha
Brought to you by:
victormote
Menu
▾
▴
[FOray-commit] SF.net SVN: foray: [8258] trunk/foray/doc/web/dev/admin/release.html
|
From: <vic...@us...> - 2006-09-30 18:29:45
|
Revision: 8258
http://svn.sourceforge.net/foray/?rev=8258&view=rev
Author: victormote
Date: 2006-09-30 11:29:41 -0700 (Sat, 30 Sep 2006)
Log Message:
-----------
Update release mechanics documentation.
Modified Paths:
--------------
trunk/foray/doc/web/dev/admin/release.html
Modified: trunk/foray/doc/web/dev/admin/release.html
===================================================================
--- trunk/foray/doc/web/dev/admin/release.html 2006-09-30 18:10:51 UTC (rev 8257)
+++ trunk/foray/doc/web/dev/admin/release.html 2006-09-30 18:29:41 UTC (rev 8258)
@@ -6,7 +6,7 @@
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
<head>
- <title>FOray: Developer Information</title>
+ <title>FOray: Release Mechanics</title>
<meta name="content-revised"
content="$Date$"/>
<!--#include virtual="/00-rsrc/include/standard-head.html" -->
@@ -20,6 +20,7 @@
<h2>Contents</h2>
<ul>
<li><a href="#before">Before</a></li>
+ <li><a href="#build">Build</a></li>
<li><a href="#after">After</a></li>
</ul>
@@ -29,16 +30,42 @@
<ol>
<li>Make sure that org.foray.common.Application.getVersion() has the correct
version number.</li>
- <li>Make sure that build scripts have the correct version number. Consider
-parameterizing the value.</li>
+ <li>Make sure that the build script build-common has the correct value for the
+ property "version".</li>
+ <li>Update the release notes.</li>
+ <li>Lock the repository or at least make a note of the repository revision
+ number which should be tagged.</li>
</ol>
+<h2><a name="build"/>Build</h2>
+<ol>
+ <li>Run the "distribution" target of the build script. The distributable
+ output should be in build/distribution.</li>
+ <li>The output should contain three files:
+ <ul>
+ <li>foray-[version]-bin-all.zip</li>
+ <li>foray-[version]-bin-modules.zip</li>
+ <li>foray-[version]-src.zip</li>
+ </ul>
+ </li>
+ <li>Run the test-dist.sh shell script. This script looks for potential
+ problems in the distribution files. If any problems are reported, fix them
+ before proceeding.</li>
+ <li>Unzip the "bin-all" distribution file, and run both the foray-test.bat
+ batch file and foray-test.sh shell script to ensure basic runnability.</li>
+</ol>
+
<h2><a name="after"/>After</h2>
<ol>
+ <li>Tag the repository.</li>
+ <li>Unlock the repository, if it was locked above.</li>
+ <li>Upload distribution file to sourceforge.</li>
+ <li>Add link to release notes on sourceforge.</li>
+ <li>Publish website to get the new release notes updated.</li>
<li>Announce the release at:
<ol>
<li>www.w3c.org</li>
- <li>the fop-dev mailing list</li>
+ <li>The foray-dev and foray-announce mailing lists.</li>
</ol>
</li>
</ol>
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|