[Crossfire-wiki] [Crossfire DokuWiki] page changed: crossfire_release_guide
no-reply_wiki at metalforge.org
no-reply_wiki at metalforge.org
Sat Apr 5 15:07:00 CDT 2014
A page in your DokuWiki was added or changed. Here are the details:
Date : 2014/04/05 15:06
User : partmedia
Edit Summary: Split up into logical sections
@@ -1,19 +1,16 @@
+ ====== Source Releases ======
+
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 ===
+ ===== 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.50.0 changes line to mark changes before/after the branch. Commit changed file:
-
- vi arch/branches/1.x/CHANGES
- svn commit Changes
-
- * For maps, regenerate a new ChangeLog:
+ * Update and commit the ChangeLog (it may be called 'CHANGES'). This can be done automatically for the maps.
- cd maps/trunk
- svn2cl.sh
+ cd maps/trunk
+ svn2cl.sh
* 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/trunk \
@@ -48,9 +45,9 @@
* If release notes for a file is needed, this appears to be done by uploading another file and noting it is a release note file
* Release of arch is now done
- === Client ===
+ ===== Client =====
Start in branches/1.x
* Update configure.ac with new version number
* Update ChangeLog file, putting in break for new version
@@ -116,22 +113,9 @@
* upload file to sourceforge, same steps, same type
* 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.
-
- //The crossfire-client.spec file requires the crossfire-client crossfire-client-sounds, crossfire-client-images tarballs to be present in a /export/home/crossfire/Crossfire directory (_sourcedir). /export/home/crossfire/RPM-TOP must also exist and contain a BUILD subdirectory. If this is not satisfactory, the %define statements for _sourcedir _srcrpmdir, _rpmdir, and _topdir may need to be locally altered to suite, but do not commit changes to SVN as the SVN settings no doubt support the actual directories used by the official client release manager.//
-
- * Make sure you have already done the client archives above, since the rpm build requires them.
- * Make crossfire-client.spec is up to date. Not that it is likely some of the paths near the top of the file may need to be changed depending on your filesystem layout.
- * Build the RPMs: ''rpmbuild -ba crossfire-client.spec''
- * 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 ===
+ ===== Server =====
Start in server/trunk
* Update ChangeLog file, putting in break for new version
* 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.
@@ -184,9 +168,9 @@
rm -rf /tmp/test
rm -rf <path>/crossfire-1.50.0
- ==== Final Notes ====
+ ===== 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.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.
@@ -194,9 +178,24 @@
* 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.
* Send mail to crossfire-announce at lists.real-time.com. Note it is a moderated alias, so there may be some time lag in the message actually appearing.
- === Windows specific things ===
+ ====== Binary Releases ======
+
+ ===== 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.
+
+ //The crossfire-client.spec file requires the crossfire-client crossfire-client-sounds, crossfire-client-images tarballs to be present in a /export/home/crossfire/Crossfire directory (_sourcedir). /export/home/crossfire/RPM-TOP must also exist and contain a BUILD subdirectory. If this is not satisfactory, the %define statements for _sourcedir _srcrpmdir, _rpmdir, and _topdir may need to be locally altered to suite, but do not commit changes to SVN as the SVN settings no doubt support the actual directories used by the official client release manager.//
+
+ * Make sure you have already done the client archives above, since the rpm build requires them.
+ * Make crossfire-client.spec is up to date. Not that it is likely some of the paths near the top of the file may need to be changed depending on your filesystem layout.
+ * Build the RPMs: ''rpmbuild -ba crossfire-client.spec''
+ * 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.
+
+ ===== Windows =====
See also [[crossfire_compile_guide#microsoft_c_windows]] for requirements.
== Client ==
IP-Address : 108.78.191.158
Old Revision: http://wiki.metalforge.net/doku.php/crossfire_release_guide?rev=1332397157
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