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

[no-reply_wiki at metalforge.org]

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

Date        : 2007/03/05 00:20
User        : 
Edit Summary: 

@@ -1,47 +1,47 @@
- Directions below have 1.10 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.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)
  
  
  === 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 changes line to mark changes before/after the branch.  Commit changed file:
+   * 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:
  
     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 -m "1.10 branch"
+    https://crossfire.svn.sourceforge.net/svnroot/crossfire/arch/tags/1.10.0 -m "1.10.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.  Note that maps directory doesn't have a CHANGES file yet:
  
-    vi arch/tags/1.10/CHANGES
-    svn commit arch/tags/1.10/CHANGES
+    vi arch/tags/1.10.0/CHANGES
+    svn commit arch/tags/1.10.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 arch
-     gtar -chvz --exclude=.svn -f crossfire-1.10.0.arch.tar.gz arch
+     ln -s 1.10.0 arch
+     gtar -chvz --exclude=.svn -f crossfire-1.10.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
+    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
+    ncftp /incoming > put crossfire-1.10.0-arch.tar.gz
     <after upload is done, quit ncftp>
  
    * 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-arch
@@ -105,8 +105,32 @@
  
      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-1.10.0-sounds.tar.gz sounds
+ 
+     * Upload sounds file like other archives - same steps, same value
+ 
+   * 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=1173074519
New Revision: http://wiki.metalforge.net/doku.php/crossfire_release_guide

-- 
This mail was generated by DokuWiki at
http://wiki.metalforge.net/