DarkRadiant Release Mechanics - Revision history

Greebo at 09:02, 5 June 2016

2016-06-05T09:02:42Z

← Older revision		Revision as of 09:02, 5 June 2016
Line 1:		Line 1:
			{{needs-update}}

	== Versions ==		== Versions ==
	DarkRadiant is using the '''major.minor.revision''' scheme for assigning version numbers to releases, e.g. 0.9.5, 1.0.2, 1.1.0, etc.		DarkRadiant is using the '''major.minor.revision''' scheme for assigning version numbers to releases, e.g. 0.9.5, 1.0.2, 1.1.0, etc.

Greebo: add PDB section

2012-09-30T08:20:29Z

add PDB section

← Older revision		Revision as of 08:20, 30 September 2012
Line 50:		Line 50:
	* Hit ''Build'' > ''Rebuild Solution'' to clear all previous intermediate files and compile DarkRadiant from scratch.		* Hit ''Build'' > ''Rebuild Solution'' to clear all previous intermediate files and compile DarkRadiant from scratch.
	* After compilation check the Output Window at the bottom if any "failed" builds are reported.		* After compilation check the Output Window at the bottom if any "failed" builds are reported.

			=== Save the PDBs ===
			It's an easy to step to miss, so keep in mind to save the .pdb files after compilation before they get overwritten by another build step. Make sure all the .pdb files from the install/ folder as well as the install/modules/ and install/plugins/ are collected. As the files can get a tad large it's best to 7zip them up and upload them to the FTP, like http://www.dramthethief.com/darkmod/files/darkradiant/darkradiant-1.7.0.x64.pdbs.7z, for Win32 and x64 separately.

			It's important to save the .pdbs for one platform before switching from Win32 to x64 (or vice versa) and kick off a new build process - it will wipe the .pdb files in the output folder, so save them before moving on to the next platform.

			TODO: create a shell script that's doing the 7zip magic automatically.

	=== Copy the Installation Binaries ===		=== Copy the Installation Binaries ===

Greebo: /* Post about the release in the TDM Editor's Guild */

2010-03-17T16:03:55Z

Post about the release in the TDM Editor's Guild

← Older revision		Revision as of 16:03, 17 March 2010
Line 79:		Line 79:
	=== Post about the release in the TDM Editor's Guild ===		=== Post about the release in the TDM Editor's Guild ===
	Tell people about the new release, there's usually a sticky for that which can be copied. Unstickify the old thread and stickify the new one.		Tell people about the new release, there's usually a sticky for that which can be copied. Unstickify the old thread and stickify the new one.

			=== Create the SVN Tag ===
			Perform an SVN copy to create the tag for the release, in the tags/ subfolder in the repository:
			https://darkradiant.svn.sourceforge.net/svnroot/darkradiant/tags/1.2.0

	== Links ==		== Links ==

Greebo: /* Windows Package Names */

2010-03-12T18:17:05Z

Windows Package Names

← Older revision		Revision as of 18:17, 12 March 2010
Line 26:		Line 26:
	* '''darkradiant-1.2.0pre1.x64.exe''' (x64)		* '''darkradiant-1.2.0pre1.x64.exe''' (x64)

	Since it's become practice to release a zipped no-installer version for each release, there is a naming convention for these ZIP files as well~~. You can use the <tt>DarkRadiant_install</tt> folders to create these ZIP packages, as created by the <tt>copy_install_files.cmd</tt> script~~.		Since it's become practice to release a zipped no-installer version for each release, there is a naming convention for these ZIP files as well.
	* '''darkradiant-1.2.0.zip''' (x86)		* '''darkradiant-1.2.0.zip''' (x86)
	* '''darkradiant-1.2.0.x64.zip''' (x64)		* '''darkradiant-1.2.0.x64.zip''' (x64)

Greebo: /* Create the Installer */

2010-03-12T18:16:47Z

Create the Installer

← Older revision		Revision as of 18:16, 12 March 2010
Line 65:		Line 65:
	* The installer is started, you can cancel that immediately.		* The installer is started, you can cancel that immediately.
	* The package has been placed in <tt>C:\Games\DarkRadiant\tools\innosetup\<packagename>.exe</tt>		* The package has been placed in <tt>C:\Games\DarkRadiant\tools\innosetup\<packagename>.exe</tt>
			=== Create the ZIP file ===
			Use the same <tt>DarkRadiant_install</tt> as base to create the ZIP files as mentioned above. Be sure not to include the folder itself, only its contents, so there should be no "DarkRadiant_install" folder within the ZIP. Also, make sure the maximum compression level is used by your zipper.

	=== Upload the Package to Sourceforge ===		=== Upload the Package to Sourceforge ===

Greebo: /* Windows Package Names */

2010-03-12T18:13:46Z

Windows Package Names

← Older revision		Revision as of 18:13, 12 March 2010
Line 26:		Line 26:
	* '''darkradiant-1.2.0pre1.x64.exe''' (x64)		* '''darkradiant-1.2.0pre1.x64.exe''' (x64)

	Since it's become practice to release a zipped no-installer version for each release, there is a naming convention for these ZIP files as well.		Since it's become practice to release a zipped no-installer version for each release, there is a naming convention for these ZIP files as well. You can use the <tt>DarkRadiant_install</tt> folders to create these ZIP packages, as created by the <tt>copy_install_files.cmd</tt> script.
	* '''darkradiant-1.2.0.zip''' (x86)		* '''darkradiant-1.2.0.zip''' (x86)
	* '''darkradiant-1.2.0.x64.zip''' (x64)		* '''darkradiant-1.2.0.x64.zip''' (x64)

Greebo: /* Links */

2010-03-10T08:26:31Z

Links

← Older revision		Revision as of 08:26, 10 March 2010
Line 81:		Line 81:
	* InnoSetup Website: http://www.jrsoftware.org/		* InnoSetup Website: http://www.jrsoftware.org/

	[[DarkRadiant]]		[[Category:DarkRadiant]]
	[[Coding]]		[[Category:Coding]]

Greebo: /* Links */

2010-03-10T08:26:17Z

Links

← Older revision		Revision as of 08:26, 10 March 2010
Line 80:		Line 80:
	== Links ==		== Links ==
	* InnoSetup Website: http://www.jrsoftware.org/		* InnoSetup Website: http://www.jrsoftware.org/

			[[DarkRadiant]]
			[[Coding]]

Greebo: /* Update the Bugtracker Project */

2010-03-10T08:25:57Z

Update the Bugtracker Project

← Older revision		Revision as of 08:25, 10 March 2010
Line 74:		Line 74:
	=== Update the Bugtracker Project ===		=== Update the Bugtracker Project ===
	Create a new version for the DarkRadiant project, and set the released on to status "released". This will remove the released project from the roadmap page. The new development version is then carrying a revision number increased by one: if the release is called 1.2.0 the new dev version will be 1.2.1.		Create a new version for the DarkRadiant project, and set the released on to status "released". This will remove the released project from the roadmap page. The new development version is then carrying a revision number increased by one: if the release is called 1.2.0 the new dev version will be 1.2.1.

			=== Post about the release in the TDM Editor's Guild ===
			Tell people about the new release, there's usually a sticky for that which can be copied. Unstickify the old thread and stickify the new one.

	== Links ==		== Links ==
	* InnoSetup Website: http://www.jrsoftware.org/		* InnoSetup Website: http://www.jrsoftware.org/

Greebo: /* Update the Website */

2010-03-10T07:50:50Z

Update the Website

← Older revision		Revision as of 07:50, 10 March 2010
Line 71:		Line 71:
	=== Update the Website ===		=== Update the Website ===
	Connect to the DarkRadiant website and adjust the download.php, index.php and latest.php files. There is also some texts to be adjusted for each release, which should present the bird's eye description of this release. Update the changelog.X.X.Y.php page for this release as well, mostly copying over the descriptions from the bugtracker changelog.		Connect to the DarkRadiant website and adjust the download.php, index.php and latest.php files. There is also some texts to be adjusted for each release, which should present the bird's eye description of this release. Update the changelog.X.X.Y.php page for this release as well, mostly copying over the descriptions from the bugtracker changelog.

			=== Update the Bugtracker Project ===
			Create a new version for the DarkRadiant project, and set the released on to status "released". This will remove the released project from the roadmap page. The new development version is then carrying a revision number increased by one: if the release is called 1.2.0 the new dev version will be 1.2.1.

	== Links ==		== Links ==
	* InnoSetup Website: http://www.jrsoftware.org/		* InnoSetup Website: http://www.jrsoftware.org/