[Crossfire-wiki] [Crossfire DokuWiki] page changed: crossfire_release_guide

no-reply_wiki at metalforge.org no-reply_wiki at metalforge.org
Mon Mar 19 02:09:14 CDT 2007 

A page in your DokuWiki was added or changed. Here are the details:

Date        : 2007/03/19 02:09
User        : 
Edit Summary: 

@@ -60,16 +60,17 @@
  
  === Client ===
  Start in branches/1.x
    * Update configure.in with new version number
+   * Update ChangeLog file, putting in break for new version
    * re-run autoconf
    * Re-run configure (needed so new version number gets embedded in Makefiles)
    * 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 -m "1.10 branch"
+    https://crossfire.svn.sourceforge.net/svnroot/crossfire/client/tags/1.10.0 -m "1.10.0 branch"
  
    * cd into the tags directory, do svn update to check out newly created branch:
  
      cd ../../tags
@@ -108,9 +109,9 @@
    * 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 branch"
+     https://crossfire.svn.sourceforge.net/svnroot/crossfire/sounds/tags/1.10.0 -m "1.10.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
  
@@ -148,5 +149,90 @@
    * If there are errors, rpmbuild will tell you.
    * Rpms would be put in _rpmdir/<architecture>
    * Upload the RPMS, architecture is the architecture, type is rpm.
  
+ == Server ==
+ Start in branches/1.x
+   * Update configure.ac with new version number
+   * Update ChangeLog file, putting in break for new version
+   * re-run autoconf
+   * 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"
+ 
+   * 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.
+   * 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
+     make collect
+   * Run ''make distcheck''.  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-client-1.10.0.tar.gz
+      cd crossfire-client-1.10.0 
+      ./configure -prefix=/tmp/test
+      make -s (make sure no errors)
+      make install (will install where specified above)
+ 
+     * run cfclient, gcfclient, gcfclient2 and make sure they are not braindead - being able to connect to a server and log in is usually what I do
+ 
+      cd /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
+ 
+   * 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 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
+ 
+     rm -f sounds
+     ln -s 1.10.0 sounds
+     gtar -chvz --exclude=.svn -f crossfire-client-sounds-1.10.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 server/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''
+     * 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
+     * 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 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   
  


IP-Address  : 209.204.178.229
Old Revision: http://wiki.metalforge.net/doku.php/crossfire_release_guide?rev=1173165684
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