[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        : 2012/03/22 01:19
User        : mwedel
Edit Summary: update directions for uploading files.

@@ -114,19 +114,9 @@
      * 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.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.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   
+   * Directions for upload in the arch and map apply for the client  
  
  === Client RPM Files ===
  
  Building the RPM is pretty straightforward.  It does require a system that actually uses RPM (like redhat).  Also, to some extent, the RPM is tied to the system it is built on, in terms of architecture and dependencies.  For example, to build the 32 bit binaries, I boot my secondary system that is only 32 bit.
@@ -187,32 +177,14 @@
       (in another window)
       gcfclient
       (create character, walk around scorn briefly)
  
-   * Upload to sourceforge FIXME - these steps have changed - but the sourceforge docs on using sftp/scp also do not work - not sure if temporary downtime or permanent change.  But files can now be updated through the files interface on sourceforge (all web based).
- 
- 
-      ncftp upload.sourceforge.net
-      ncftp / > cd incoming
-      ncftp /incoming > put crossfire-1.50.0.tar.gz
-      <after upload is done, quit ncftp>
+   * The upload directions for the arch and map apply for the client  
  
    * Clean up some files:
  
      rm -rf /tmp/test
      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.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.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.


IP-Address  : 173.228.106.67
Old Revision: http://wiki.metalforge.net/doku.php/crossfire_release_guide?rev=1332050978
New Revision: http://wiki.metalforge.net/doku.php/crossfire_release_guide

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