ReleasingWesnoth - Revision history

Soliton: /* Cleanup and post release steps */

2025-02-07T07:20:53Z

Cleanup and post release steps

← Older revision		Revision as of 07:20, 7 February 2025
Line 267:		Line 267:

	Contact shadowm or Soliton to update the MP servers' configuration to allow users of the new release or rebuild the servers as needed (only required for development releases).		Contact shadowm or Soliton to update the MP servers' configuration to allow users of the new release or rebuild the servers as needed (only required for development releases).

			Update [[TerrainCodeTableWML]] with <code>data/tools/terrain2wiki.py</code>.

	== The real announcement ==		== The real announcement ==

Soliton: Link to new page so there is a chance to find it.

2024-07-27T13:51:11Z

Link to new page so there is a chance to find it.

← Older revision		Revision as of 13:51, 27 July 2024
Line 1:		Line 1:
			== This page is not maintained anymore. See [[Release_Steps]]. ==

	== todo steps to add ==		== todo steps to add ==

Loonycyborg at 18:08, 14 February 2020

2020-02-14T18:08:00Z

← Older revision		Revision as of 18:08, 14 February 2020
Line 194:		Line 194:

	data/tools/about_cfg_to_wiki -w <PATH TO GAME EXECUTABLE> > about.wiki		data/tools/about_cfg_to_wiki -w <PATH TO GAME EXECUTABLE> > about.wiki

			== Alternative post-tag package creation method ==

			This method requires tagging release before generating tarballs and doing uploads. It involves running a single script but this script needs to be modified each time to update versions. It also requires existing tarball of previous release against which to create xdelta.

			#!/bin/sh -xe
			VERSION=1.15.2
			OLDVERSION=1.15.1
			git checkout $VERSION
			git archive --format=tar --prefix="wesnoth-$VERSION/" $VERSION > "wesnoth-$VERSION.tar"
			bunzip2 wesnoth-$OLDVERSION.tar.bz2
			xdelta delta wesnoth-$OLDVERSION.tar wesnoth-$VERSION.tar wesnoth-$OLDVERSION.tar-wesnoth-$VERSION.tar.xdelta \|\| true
			bzip2 wesnoth-$VERSION.tar
			sha256sum wesnoth-$VERSION.tar.bz2 > wesnoth-$VERSION.tar.bz2.sha256
			scp -P 10222 wesnoth-$VERSION.tar.bz2 wesnoth-$OLDVERSION.tar-wesnoth-$VERSION.tar.xdelta loonycyborg@wesnoth.org:/srv/www/html/files/
			scp -P 10222 wesnoth-$VERSION.tar.bz2.sha256 YOUR_WESNOTH_ORG_USERNAME@wesnoth.org:/srv/www/html/files/releases/
			rsync -avP -e ssh wesnoth-$VERSION.tar.bz2 wesnoth-$VERSION.tar.bz2.sha256 wesnoth-$OLDVERSION.tar-wesnoth-$VERSION.tar.xdelta YOUR_SF_USERNAME,wesnoth@frs.sourceforge.net:/home/frs/project/w/we/wesnoth/wesnoth/wesnoth-$VERSION/

	== Notify packagers ==		== Notify packagers ==

Josteph: /* todo steps to add */

2019-10-20T03:14:36Z

todo steps to add

← Older revision		Revision as of 03:14, 20 October 2019
Line 15:		Line 15:
	* Updating the download page on the wiki		* Updating the download page on the wiki
	* Updating the front page		* Updating the front page
	* rebuild the front page (`git pull` and `make` after SSHing to www.wesnoth.org)		* rebuild the front page (<code>git pull</code> and <code>make</code> after SSHing to www.wesnoth.org)
	* Announcing the release on Discord		* Announcing the release on Discord
	* Announcing the release on Steam.		* Announcing the release on Steam.

Josteph: /* todo steps to add */

2019-10-20T03:14:20Z

todo steps to add

← Older revision		Revision as of 03:14, 20 October 2019
Line 15:		Line 15:
	* Updating the download page on the wiki		* Updating the download page on the wiki
	* Updating the front page		* Updating the front page
	* rebuild the front page (~~ask Iris~~)		* rebuild the front page (`git pull` and `make` after SSHing to www.wesnoth.org)
	* Announcing the release on Discord		* Announcing the release on Discord
	* Announcing the release on Steam.		* Announcing the release on Steam.

Celtic Minstrel: /* todo steps to add */ Fixup formatting

2019-10-20T03:06:36Z

todo steps to add: Fixup formatting

← Older revision		Revision as of 03:06, 20 October 2019
Line 11:		Line 11:
	For us:		For us:

	- forum post in News		* forum post in News
	- forum post in Announcements		* forum post in Announcements
	- Updating the download page on the wiki		* Updating the download page on the wiki
	- Updating the front page		* Updating the front page
	- rebuild the front page (ask Iris)		* rebuild the front page (ask Iris)
	- Announcing the release on Discord		* Announcing the release on Discord
	- Announcing the release on Steam.		* Announcing the release on Steam.
	- This included making a new header graphic if it's a stable release.		** This included making a new header graphic if it's a stable release.
	- Announcing the release on Twitter with a link to the forum post		* Announcing the release on Twitter with a link to the forum post


	== Version numbering ==		== Version numbering ==

Josteph: todo

2019-10-20T03:05:37Z

todo

← Older revision		Revision as of 03:05, 20 October 2019
Line 1:		Line 1:
			== todo steps to add ==

			Mac package: details in projectfiles/Xcode/README.md

			Windows package: ?

			Android package: (third party, but still, details?)

			iOS package: ?

			For us:

			- forum post in News
			- forum post in Announcements
			- Updating the download page on the wiki
			- Updating the front page
			- rebuild the front page (ask Iris)
			- Announcing the release on Discord
			- Announcing the release on Steam.
			- This included making a new header graphic if it's a stable release.
			- Announcing the release on Twitter with a link to the forum post


	== Version numbering ==		== Version numbering ==

Josteph: /* Notify packagers */

2019-10-08T19:40:45Z

Notify packagers

← Older revision		Revision as of 19:40, 8 October 2019
Line 180:		Line 180:

	'''NOTE:''' Make sure that our "tier 1" packagers (currently Windows and OS X) whose content is hosted by us on SF.net upload the SHA256 sums of their files to files.wesnoth.org/releases/ as well!		'''NOTE:''' Make sure that our "tier 1" packagers (currently Windows and OS X) whose content is hosted by us on SF.net upload the SHA256 sums of their files to files.wesnoth.org/releases/ as well!

			'''TODO:''' Upload not just the sha256 files but also the actual files, as a backup in case sf.net is down etc

	=== Example messages ===		=== Example messages ===

Octalot: /* Preparation steps */ 1.15.3 will start the 1.16.0 string freeze

2019-10-08T13:16:53Z

Preparation steps: 1.15.3 will start the 1.16.0 string freeze

← Older revision		Revision as of 13:16, 8 October 2019
Line 55:		Line 55:
	* Merge the fixes on [[SpellingMistakes]]		* Merge the fixes on [[SpellingMistakes]]
	* Review issues in the relevant labels (probably these? [https://github.com/wesnoth/wesnoth/labels/Blocker Blocker], [https://github.com/wesnoth/wesnoth/labels/Regression Regression], [https://github.com/wesnoth/wesnoth/labels/Urgent Urgent], and either [https://github.com/wesnoth/wesnoth/labels/Fwdport Fwdport] or [https://github.com/wesnoth/wesnoth/labels/Backport Backport] depending on what branch you're releasing) and milestones (for example, [https://github.com/wesnoth/wesnoth/milestone/9 1.15.2] and [https://github.com/wesnoth/wesnoth/milestone/13 1.16.0], if a development release; just [https://github.com/wesnoth/wesnoth/milestone/17 1.14.9], if a stable release).		* Review issues in the relevant labels (probably these? [https://github.com/wesnoth/wesnoth/labels/Blocker Blocker], [https://github.com/wesnoth/wesnoth/labels/Regression Regression], [https://github.com/wesnoth/wesnoth/labels/Urgent Urgent], and either [https://github.com/wesnoth/wesnoth/labels/Fwdport Fwdport] or [https://github.com/wesnoth/wesnoth/labels/Backport Backport] depending on what branch you're releasing) and milestones (for example, [https://github.com/wesnoth/wesnoth/milestone/9 1.15.2] and [https://github.com/wesnoth/wesnoth/milestone/13 1.16.0], if a development release; just [https://github.com/wesnoth/wesnoth/milestone/17 1.14.9], if a stable release).
			** For 1.15.3, review the [https://github.com/wesnoth/wesnoth/milestone/20 pre-1.16.0 string freeze] issues
	* Review the list of issues for the ''previous'' patch release (1.15.1 or 1.14.8), make sure it's empty.		* Review the list of issues for the ''previous'' patch release (1.15.1 or 1.14.8), make sure it's empty.
	* Make sure to run and commit a pot-update (see above), and update to the latest revision of the branch if needed. At this point you should warn people to stop pushing commits to the branch you'll be using for the release so as to avoid last-minute work sync issues or new unexpected bugs.		* Make sure to run and commit a pot-update (see above), and update to the latest revision of the branch if needed. At this point you should warn people to stop pushing commits to the branch you'll be using for the release so as to avoid last-minute work sync issues or new unexpected bugs.

Josteph: /* Version numbering */

2019-10-06T20:04:25Z

Version numbering

← Older revision		Revision as of 20:04, 6 October 2019
Line 9:		Line 9:
	A development version should be called "release candidate 1" when all blockers have been fixed.		A development version should be called "release candidate 1" when all blockers have been fixed.

	No API changes (e.g., Lua/WML interfaces or semantics) should be made ~~during the beta/RC/stable stage~~, nor large-scale or destabilizing internal changes, nor build dependencies changed. That's true from "1.15.x (1.16 beta 1)" and for the rest of the 1.16.x releases too. Such changes should be made in 1.17.x for 1.18.		During the beta/RC/stable stages, no API changes (e.g., Lua/WML interfaces or semantics) should be made , nor large-scale or destabilizing internal changes, nor build dependencies changed. That's true from "1.15.x (1.16 beta 1)" and for the rest of the 1.16.x releases too. Such changes should be made in 1.17.x for 1.18.

	== Tools ==		== Tools ==