[Crossfire-wiki] [Crossfire DokuWiki] page changed: crossfire_release_guide
no-reply_wiki at metalforge.org
no-reply_wiki at metalforge.org
Mon Apr 26 01:07:33 CDT 2010
A page in your DokuWiki was added or changed. Here are the details:
Date : 2010/04/26 01:07
User :
Edit Summary: update for version 1.50 strings, release based on trunk
@@ -1,47 +1,39 @@
- Directions below have 1.10.0 as the example release. Directions of commands below presume you start in the top level SVN directory (the one that contains the arch, client, maps, server) for each phase (arch, client, maps, server)
+ Directions below have 1.50.0 as the example release. Directions of commands below presume you start in the top level SVN directory (the one that contains the arch, client, maps, server) for each phase (arch, client, maps, server)
=== Arch & Maps ===
The process for both the arch and maps directory is the same - the only difference is the name of the files/paths.
- * Update the CHANGES in the branches/1.x to add a 1.10.0 changes line to mark changes before/after the branch. Commit changed file:
+ * Update the CHANGES in the branches/1.x to add a 1.50.0 changes line to mark changes before/after the branch. Commit changed file:
vi arch/branches/1.x/CHANGES
svn commit Changes
* Make a copy of the repository. Note this does a copy on the server, so if your local copy is a out of sync, it won't matter.
- svn copy https://crossfire.svn.sourceforge.net/svnroot/crossfire/arch/branches/1.x \
- https://crossfire.svn.sourceforge.net/svnroot/crossfire/arch/tags/1.10.0 -m "1.10.0 branch"
+ svn copy https://crossfire.svn.sourceforge.net/svnroot/crossfire/arch/trunk \
+ https://crossfire.svn.sourceforge.net/svnroot/crossfire/arch/tags/1.50.0 -m "1.50.0 branch"
* Check out the tag, so you now have a local copy:
svn update arch/tags
* Update the Changelog to change it (no top of SVN) in branch.
- vi arch/tags/1.10.0/CHANGES
- svn commit arch/tags/1.10.0/CHANGES
+ vi arch/tags/1.50.0/CHANGES
+ svn commit arch/tags/1.50.0/CHANGES
* Make archive of arch/maps directory. Note we want the arch directory called 'arch/maps' in the archive, hence the symlink. Gnu tar is used:
cd arch/tags
rm -f arch
- ln -s 1.10.0 arch
- gtar -chvz --exclude=.svn -f crossfire-1.10.0.arch.tar.gz arch
+ ln -s 1.50.0 arch
+ gtar -chvz --exclude=.svn -f crossfire-1.50.0.arch.tar.gz arch
* Maps only - we want a bzip2 copy because it saves considerable space. This may take a little while depending on speed of your system. You can start on the next stage of uploaded the .gz file while this is processing:
- gunzip -c crossfire-1.10.0.maps.tar.gz | bzip2 -c9 > crossfire-1.10.0.maps.tar.bz2
-
- * Upload the file to sourceforge. If doing the maps, also upload the .bz2 file:
-
- ncftp upload.sourceforge.net
- <login message omitted>
- ncftp / > cd incoming
- ncftp /incoming > put crossfire-1.10.0-arch.tar.gz
- <after upload is done, quit ncftp>
+ gunzip -c crossfire-1.50.0.maps.tar.gz | bzip2 -c9 > crossfire-1.50.0.maps.tar.bz2
* Make a file release on sourceforge. Go to crossfire, Project Admin, File Manager
* Use the file browser interface to navigate to the correct directory.
* Left click on the gear icon to make a directory in the correct location. Follow existing naming convention.
@@ -62,23 +54,23 @@
* Update crossfire-client.spec with new version
* Run ''svn commit'' to commit configure, Changelog, crossfire-client.spec changes.
* Make a copy of the repository. Note this does a copy on the server, so if your local copy is a out of sync, it won't matter.
- svn copy https://crossfire.svn.sourceforge.net/svnroot/crossfire/client/branches/1.x \
- https://crossfire.svn.sourceforge.net/svnroot/crossfire/client/tags/1.10.0 -m "1.10.0 branch"
+ svn copy https://crossfire.svn.sourceforge.net/svnroot/crossfire/client/trunk \
+ https://crossfire.svn.sourceforge.net/svnroot/crossfire/client/tags/1.50.0 -m "1.50.0 branch"
* cd into the tags directory, do svn update to check out newly created branch:
cd ../../tags
svn update
- * Clean up ChangeLog - remove top of SVN line, instead just have ''Changes for 1.10.0'' be at the top.
+ * Clean up ChangeLog - remove top of SVN line, instead just have ''Changes for 1.50.0'' be at the top.
* Run configure. Options are not really important.
- * Run ''make dist''. This will create a crossfire-client-1.10.0.tar.gz in the current directory.
+ * Run ''make dist''. This will create a crossfire-client-1.50.0.tar.gz in the current directory.
* Unpack the archive, and verify it works:
- gtar xvfz crossfire-client-1.10.0.tar.gz
- cd crossfire-client-1.10.0
+ gtar xvfz crossfire-client-1.50.0.tar.gz
+ cd crossfire-client-1.50.0
./configure -prefix=/tmp/test
make -s (make sure no errors)
make install (will install where specified above)
@@ -87,52 +79,45 @@
cd /tmp/test/bin
./cfclient
./gcfclient
./gcfclient2
-
- * If all OK, upload the crossfire-client-1.10.0.tar.gz
-
- ncftp upload.sourceforge.net
- ncftp / > cd incoming
- ncftp /incoming > put crossfire-1.10.0.arch.tar.gz
- <after upload is done, quit ncftp>
* Clean up some files:
rm -rf /tmp/test
- rm -rf <path>/crossfire-client-1.10.0
+ rm -rf <path>/crossfire-client-1.50.0
* Make sounds archive - may seem pointless since sounds are not changing, but the the rpm build process basically requires that there be a sounds archive with the same release number.
* Make copy of the repository:
svn copy https://crossfire.svn.sourceforge.net/svnroot/crossfire/sounds/trunk \
- https://crossfire.svn.sourceforge.net/svnroot/crossfire/sounds/tags/1.10.0 -m "1.10.0 branch"
+ https://crossfire.svn.sourceforge.net/svnroot/crossfire/sounds/tags/1.50.0 -m "1.50.0 branch"
* Run svn update in sounds/tags to download the sounds.
- * Like the arch area above, we expect the sounds to be in a directory called sounds, not 1.10.0
+ * Like the arch area above, we expect the sounds to be in a directory called sounds, not 1.50.0
rm -f sounds
- ln -s 1.10.0 sounds
- gtar -chvz --exclude=.svn -f crossfire-client-sounds-1.10.0.tar.gz sounds
+ ln -s 1.50.0 sounds
+ gtar -chvz --exclude=.svn -f crossfire-client-sounds-1.50.0.tar.gz sounds
* Upload sounds file to sourceforge - same as other files - same steps, same value
* Make an image archive for the client. Needed for RPM building. Need a server tree with a properly linked arch tree.
* ''cd lib; adm/collect_images.pl -archive''
* that will create a ../crossfire-images.tar file
- * rename file: ''mv crossfire-images.tar crossfire-client-images-1.10.0.tar''
- * compress to file: ''gzip -v9 crossfire-client-images-1.10.0.tar''
+ * rename file: ''mv crossfire-images.tar crossfire-client-images-1.50.0.tar''
+ * compress to file: ''gzip -v9 crossfire-client-images-1.50.0.tar''
* upload file to sourceforge, same steps, same type
* Make a file release on sourceforge. Go to [[ http://sourceforge.net/project/admin/editpackages.php?group_id=13833|File Release System]]
* Add a release to crossfire-client
- * Release name is 1.10.0
- * For release notes, generally do something like ''1.10.0 release or archetype tree for crossfire''. I'll also include notable changes
+ * Release name is 1.50.0
+ * For release notes, generally do something like ''1.50.0 release or archetype tree for crossfire''. I'll also include notable changes
* For Changelog, copy portion of CHANGES that has changed since last release
* Check button to preserve preformatted text.
* Hit checkbox to preserve preformatted text.
* Hit refresh before continuing onto selecting file to upload.
- * Select crossfire-1.10.0.client.tar.gz from list of files, hit Add Files button.
+ * Select crossfire-1.50.0.client.tar.gz from list of files, hit Add Files button.
* Select Any for processor type, Source.gz for file type, hit Update/refresh.
* Check box to send e-mail to users monitoring, hit button to send e-mail
=== Client RPM Files ===
@@ -157,30 +142,30 @@
* Re-run configure (needed so new version number gets embedded in Makefiles)
* Run ''svn commit'' to commit configure, Changelog, configure.ac changes.
* Make a copy of the repository. Note this does a copy on the server, so if your local copy is a out of sync, it won't matter.
- svn copy https://crossfire.svn.sourceforge.net/svnroot/crossfire/server/branches/1.x \
- https://crossfire.svn.sourceforge.net/svnroot/crossfire/server/tags/1.10.0 -m "1.10.0 branch"
+ svn copy https://crossfire.svn.sourceforge.net/svnroot/crossfire/server/trunk \
+ https://crossfire.svn.sourceforge.net/svnroot/crossfire/server/tags/1.50.0 -m "1.50.0 branch"
* cd into the tags directory, do svn update to check out newly created branch:
cd ../../tags
svn update
- * Clean up ChangeLog - remove top of SVN line, instead just have ''Changes for 1.10.0'' be at the top.
+ * Clean up ChangeLog - remove top of SVN line, instead just have ''Changes for 1.50.0'' be at the top.
* Run configure. Options are not really important.
* Since distributions include prebuilt archetypes, need to rebuild them:
cd lib
- ln -s ../../../../arch/tags/1.10.0 arc
+ ln -s ../../../../arch/tags/1.50.0 arc
make collect
* Run ''make distcheck'' from top level directory. This will pack up the distribution and then unpack it and compile it - a pretty good complete test.
* Unpack the archive, and verify it works:
- gtar xvfz crossfire-1.10.0.tar.gz
- cd crossfire-1.10.0
+ gtar xvfz crossfire-1.50.0.tar.gz
+ cd crossfire-1.50.0
./configure -prefix=/tmp/test
make -s (make sure no errors)
make install (will install where specified above)
@@ -199,32 +184,32 @@
ncftp upload.sourceforge.net
ncftp / > cd incoming
- ncftp /incoming > put crossfire-1.10.0.tar.gz
+ ncftp /incoming > put crossfire-1.50.0.tar.gz
<after upload is done, quit ncftp>
* Clean up some files:
rm -rf /tmp/test
- rm -rf <path>/crossfire-1.10.0
+ rm -rf <path>/crossfire-1.50.0
* Make a file release on sourceforge. Go to [[ http://sourceforge.net/project/admin/editpackages.php?group_id=13833|File Release System]]
* Add a release to crossfire-client
- * Release name is 1.10.0
- * For release notes, generally do something like ''Release of 1.10.0 of the crossfire game server. You do not need this if you just want to play on a remote server.''.
+ * Release name is 1.50.0
+ * For release notes, generally do something like ''Release of 1.50.0 of the crossfire game server. You do not need this if you just want to play on a remote server.''.
* For Changelog, copy portion of CHANGES that has changed since last release
* Check button to preserve preformatted text.
* Hit checkbox to preserve preformatted text.
* Hit refresh before continuing onto selecting file to upload.
- * Select crossfire-1.10.0.tar.gz from list of files, hit Add Files button.
+ * Select crossfire-1.50.0.tar.gz from list of files, hit Add Files button.
* Select Any for processor type, Source.gz for file type, hit Update/refresh.
* Check box to send e-mail to users monitoring, hit button to send e-mail
==== Final Notes ====
After all the components are bundled up, an official announcement is sent to crossfire-announce at lists.real-time.com. I usually use the announcement of the last release as a template.
- * Update 1.9.1 to 1.10.0
+ * Update 1.11.0 to 1.50.0
* generate a sum of the files. I put all of them in one directory, so it is just a simple ''sum *'' and remove any extra entries that shouldn't be there.
* Same for md5sums - ''md5sum *''
* At the top of the file, put in the notable changes - note you may already have these from the steps above.
* At end of file, put in complete changelog file.
@@ -247,9 +232,9 @@
* open NSI project file ''gtk/win32/gtkclient.nsi''
* change version number (lines 8, 13, 15)
* create installer
* ensure it works correctly
- * rename installer to ''crossfire-client-1.10.0.exe''
+ * rename installer to ''crossfire-client-1.50.0.exe''
* upload to Sourceforge
* create a release
* paste ''Win32Changes.txt'' to readme part, Changelog to changelog part
* release
@@ -268,9 +253,9 @@
* open the NSIS project file ''make_win32/cfserver.nsi''
* fix version number (lines 4, 9, 11)
* build installer
* ensure installer works correctly
- * rename exe to ''crossfire-server-1.10.0.exe''
+ * rename exe to ''crossfire-server-1.50.0.exe''
* upload to Sourceforge
* create release
* copy ''Changelog'' to changelog part, ''Release_notes.txt'' to readme
* release
@@ -280,9 +265,9 @@
* from server code, run the ''make_win32/make_maps_nsi.pl'' file (syntax: ''make_maps_nsi.pl "Big World maps" ..\..\share\maps'' if you installed maps in share)
* build generated .NSI file
* ensure installer works fine
- * rename executable to ''crossfire-server-bigworld-maps-1.10.0.exe''
+ * rename executable to ''crossfire-server-bigworld-maps-1.50.0.exe''
* upload to Sourceforge
* add to previous release
* send notification
IP-Address : 76.191.154.198
Old Revision: http://wiki.metalforge.net/doku.php/crossfire_release_guide?rev=1272259664
New Revision: http://wiki.metalforge.net/doku.php/crossfire_release_guide
--
This mail was generated by DokuWiki at
http://wiki.metalforge.net/
More information about the crossfire-wiki
mailing list