Support:Releasing: Difference between revisions
Content deleted Content added
imported>Hendrik Brummermann Created page with "{{Likely Outdated}} From /home/marauroa/doc/releasing.txt <pre> Preparing for release Announce a code freeze (allow bug fixes only) Ask testers to test everything new and every..." |
imported>Hendrik Brummermann started to convert into wiki formating |
||
Line 3:
From /home/marauroa/doc/releasing.txt
== Preparing for release ==▼
<pre>▼
▲Preparing for release
Announce a code freeze (allow bug fixes only)▼
Ask testers to test everything new and everything old▼
Ask developers to update doc/CHANGES.txt▼
Ask testers to make nice screenshots of the changes▼
=== Announcements ===
Version numbers▼
The correct way to change version numbers is to edit build.ant.properties then run ant dist.▼
▲* Announce a code freeze (allow bug fixes only)
▲* Ask testers to test everything new and everything old
▲* Ask developers to update doc/CHANGES.txt
▲* Ask testers to make nice screenshots of the changes
▲=== Version numbers ===
▲The correct way to change version numbers is to edit build.ant.properties then run ant init (or ant dist).
You edit the lines
version
I am sure I don't need to explain the numbers or names to you, it is self evident.
=== Branching procedure ===
We develop code on HEAD and branch from HEAD for each release.
We develop code on HEAD and branch from HEAD for each release. Eclipse is a good way to branch: from a HEAD checkout, right click and select Team -> Branch. Click details .. to see the names of existing branches, like VERSION_00_RELEASE_XX, so that you are sure you're choosing a name for the new branch which sticks with conventions. Ensure your cvs timeout is sufficiently large that the branching prcoess can complete. ▼
Once branch is successfully created, one can can update their IDE to use that branch (follow your IDE instructions for this) or for command line cvs, run▼
▲
▲Once branch is successfully created, one can can update their IDE to use that branch (follow your IDE instructions for this) or for command line cvs, run cvs update -rVERSION_00_RELEASE_XX -Pd
on your existing HEAD checkout to change it to be for the XX release.
== Releasing ==
Building the release▼
▲=== Building the release ===
Normally when you build the client or server, ant clean && build is enough. For release we need to build many things - not just the server and client but also the server source code, zipped up, the .jnlp file for webstart, and signed jars so that updates work correctly. A signed jar needs a 'key'. This is inside a file called keystore.ks which you can only get from people trusted by the Sun corporation. If you are a Stendhal project admin please ask Miguel for this file. It is placed in the same directory as build.xml etc - i.e. your root stendhal source directory. A keystore alias and password is expected. You can put these as parameters everytime you run ant dist (see below) or in a file called build.ant-private.properties (ask hendrik about this).
▲<pre>
Now you are ready to run:
ant dist -Dkeystore.alias=miguelangelblanchlardin@hotmail.com -Dkeystore.password=qwerty
You should now have the 4 files for the file release:
Line 37 ⟶ 44:
the 2 client zips, build/stendhal-FULL-0.XX.zip and build/stendhal-0.XX.zip
the source gzip, at build/stendhal-0.XX-src.tar.gz
</pre>
=== Uploading the File Release ===
You need to get the folder ready for the files to go in. You can:
<pre>
Make a shell session using
ssh -t kymara,arianne@shell.sourceforge.net create
Line 127 ⟶ 139:
</pre>
=== After Release ===
{{TODO|Notify arianne-announce email list, Sourceforge Project News Feed, Twitter, [[Support:Pages_covering_Stendhal]]}}
| |||