Joomla:Release procedure and checklist - Revision history

M-b-o: Protected "Joomla:Release procedure and checklist" ([Edit=Allow only editor users] (indefinite) [Move=Allow only editor users] (indefinite))

2022-08-15T18:55:29Z

Protected "Joomla:Release procedure and checklist" ([Edit=Allow only editor users] (indefinite) [Move=Allow only editor users] (indefinite))

← Older revision	Revision as of 18:55, 15 August 2022
(No difference)

Wilsonge: /* Onboarding Release Leads */

2022-02-12T22:41:00Z

Onboarding Release Leads

← Older revision		Revision as of 22:41, 12 February 2022
Line 181:		Line 181:
	* Glip (CMS Maintainers, CMS Release Leads, WebMasters Team, Production, CMS Release Team)		* Glip (CMS Maintainers, CMS Release Leads, WebMasters Team, Production, CMS Release Team)
	* Introduction with Translation, JSST and Webmaster Liasons		* Introduction with Translation, JSST and Webmaster Liasons
	* SSH keys added to Update and Downloads servers		* SSH keys added to Update and Downloads servers (including VPN Access)
	* Downloads Website (Release Leads -> CMS ACL Group)		* Downloads Website (Release Leads -> CMS ACL Group)
	* Developer Website (? ACL Group)		* Developer Website (? ACL Group)

Wilsonge: /* Onboarding Release Leads */

2022-01-30T19:54:02Z

Onboarding Release Leads

← Older revision		Revision as of 19:54, 30 January 2022
Line 178:		Line 178:
	Release Leads will need access to a number of resources. The following are required:		Release Leads will need access to a number of resources. The following are required:
	* Account on Github (added to [https://github.com/orgs/joomla/teams/cms-release-leads/members the CMS Release Leads team] for the Joomla Org (which also provides jenkins access) and [https://github.com/orgs/joomla-backports/teams/cms-release-leads the CMS Release Leads team] for the Joomla Backport org.		* Account on Github (added to [https://github.com/orgs/joomla/teams/cms-release-leads/members the CMS Release Leads team] for the Joomla Org (which also provides jenkins access) and [https://github.com/orgs/joomla-backports/teams/cms-release-leads the CMS Release Leads team] for the Joomla Backport org.
	* The Forum (Ensure users are aware of release ~~groups~~)		* The Forum (Ensure users are aware of release threads)
	* Glip (CMS Maintainers, CMS Release Leads, WebMasters Team, ~~JSST~~)		* Glip (CMS Maintainers, CMS Release Leads, WebMasters Team, Production, CMS Release Team)
	* Introduction with Translation, JSST and Webmaster Liasons		* Introduction with Translation, JSST and Webmaster Liasons
	* SSH keys added to Update and Downloads servers		* SSH keys added to Update and Downloads servers
	* Downloads Website (Release Leads -> CMS ACL Group)		* Downloads Website (Release Leads -> CMS ACL Group)
			* Developer Website (? ACL Group)
	* AWS Account in Release_Managers Group. User must reset password and setup MFA.		* AWS Account in Release_Managers Group. User must reset password and setup MFA.
			* Drone Admins

	[[Category:Bug Squad]]		[[Category:Bug Squad]]
	[[Category:Coordinators]]		[[Category:Coordinators]]
	[[Category:Development]]		[[Category:Development]]

Wilsonge: /* Onboarding Release Leads */

2022-01-30T17:54:22Z

Onboarding Release Leads

← Older revision		Revision as of 17:54, 30 January 2022
Line 183:		Line 183:
	* SSH keys added to Update and Downloads servers		* SSH keys added to Update and Downloads servers
	* Downloads Website (Release Leads -> CMS ACL Group)		* Downloads Website (Release Leads -> CMS ACL Group)
	* AWS Account in Release_Managers Group		* AWS Account in Release_Managers Group. User must reset password and setup MFA.

	[[Category:Bug Squad]]		[[Category:Bug Squad]]
	[[Category:Coordinators]]		[[Category:Coordinators]]
	[[Category:Development]]		[[Category:Development]]

Wilsonge: /* Onboarding Release Leads */

2022-01-30T17:53:33Z

Onboarding Release Leads

← Older revision		Revision as of 17:53, 30 January 2022
Line 177:		Line 177:
	== Onboarding Release Leads ==		== Onboarding Release Leads ==
	Release Leads will need access to a number of resources. The following are required:		Release Leads will need access to a number of resources. The following are required:
	- Account on Github (added to [https://github.com/orgs/joomla/teams/cms-release-leads/members the CMS Release Leads team] for the Joomla Org (which also provides jenkins access) and [https://github.com/orgs/joomla-backports/teams/cms-release-leads the CMS Release Leads team] for the Joomla Backport org.		* Account on Github (added to [https://github.com/orgs/joomla/teams/cms-release-leads/members the CMS Release Leads team] for the Joomla Org (which also provides jenkins access) and [https://github.com/orgs/joomla-backports/teams/cms-release-leads the CMS Release Leads team] for the Joomla Backport org.
	- The Forum (Ensure users are aware of release groups)		* The Forum (Ensure users are aware of release groups)
	- Glip (CMS Maintainers, CMS Release Leads, WebMasters Team, JSST)		* Glip (CMS Maintainers, CMS Release Leads, WebMasters Team, JSST)
	- Introduction with Translation, JSST and Webmaster Liasons		* Introduction with Translation, JSST and Webmaster Liasons
	- SSH keys added to Update and Downloads servers		* SSH keys added to Update and Downloads servers
	- Downloads Website (Release Leads -> CMS ACL Group)		* Downloads Website (Release Leads -> CMS ACL Group)
	- AWS Account in Release_Managers Group		* AWS Account in Release_Managers Group

	[[Category:Bug Squad]]		[[Category:Bug Squad]]
	[[Category:Coordinators]]		[[Category:Coordinators]]
	[[Category:Development]]		[[Category:Development]]

Wilsonge at 17:53, 30 January 2022

2022-01-30T17:53:08Z

← Older revision		Revision as of 17:53, 30 January 2022
Line 4:		Line 4:

	There is a more formal checklist available [https://github.com/joomla/joomla-cms/blob/4.1-dev/build/release-checklist.md on GitHub] for release leads to use that is intended to complement the steps described in this page.		There is a more formal checklist available [https://github.com/joomla/joomla-cms/blob/4.1-dev/build/release-checklist.md on GitHub] for release leads to use that is intended to complement the steps described in this page.

	Release Leads will need access to a number of resources. But accounts on Github (and being added to [https://github.com/orgs/joomla/teams/cms-release-leads/members the CMS Release Leads team] - which also provides jenkins access), the Forum and Glip are effectively mandatory.

	~~= CMS Release Cycle =~~

	== Issue Triage, Patch Review, Merging Patches ==		== Issue Triage, Patch Review, Merging Patches ==
Line 178:		Line 174:
	== Security Releases ==		== Security Releases ==
	When a security release is created, a pull request should be sent to the [https://github.com/FriendsOfPHP/security-advisories FriendsOfPHP/security-advisories repository] with relevant details. This repository is used by many tools in the PHP and Composer ecosystem to alert users of security issues. https://github.com/FriendsOfPHP/security-advisories/pull/134 is an example of this pull request.		When a security release is created, a pull request should be sent to the [https://github.com/FriendsOfPHP/security-advisories FriendsOfPHP/security-advisories repository] with relevant details. This repository is used by many tools in the PHP and Composer ecosystem to alert users of security issues. https://github.com/FriendsOfPHP/security-advisories/pull/134 is an example of this pull request.

			== Onboarding Release Leads ==
			Release Leads will need access to a number of resources. The following are required:
			- Account on Github (added to [https://github.com/orgs/joomla/teams/cms-release-leads/members the CMS Release Leads team] for the Joomla Org (which also provides jenkins access) and [https://github.com/orgs/joomla-backports/teams/cms-release-leads the CMS Release Leads team] for the Joomla Backport org.
			- The Forum (Ensure users are aware of release groups)
			- Glip (CMS Maintainers, CMS Release Leads, WebMasters Team, JSST)
			- Introduction with Translation, JSST and Webmaster Liasons
			- SSH keys added to Update and Downloads servers
			- Downloads Website (Release Leads -> CMS ACL Group)
			- AWS Account in Release_Managers Group

	[[Category:Bug Squad]]		[[Category:Bug Squad]]
	[[Category:Coordinators]]		[[Category:Coordinators]]
	[[Category:Development]]		[[Category:Development]]

Wilsonge: /* Maintenance Release */

2022-01-30T11:36:25Z

Maintenance Release

← Older revision		Revision as of 11:36, 30 January 2022
Line 52:		Line 52:
	Maintenance releases operate on a 4-6 week cycle and the following is the suggested release timeline:		Maintenance releases operate on a 4-6 week cycle and the following is the suggested release timeline:

	* 7 days before planned release date: Tag a Release Candidate		* 9-10 days before planned release date: Tag a Release Candidate
	** With the Release Candidate, language freeze is also in effect and no language changes are permitted unless there is an urgent need (which should be communicated with the translations coordinator); note that if necessary the language freeze may be declared earlier but the Release Candidate should be considered the "no later than" time		** With the Release Candidate, language freeze is also in effect and no language changes are permitted unless there is an urgent need (which should be communicated with the translations coordinator); note that if necessary the language freeze may be declared earlier but the Release Candidate should be considered the "no later than" time
	** Inform the CMS Release Team and call out anything that you would like extra testing on		** Inform the CMS Release Team and call out anything that you would like extra testing on

Wilsonge at 01:30, 30 January 2022

2022-01-30T01:30:47Z

← Older revision		Revision as of 01:30, 30 January 2022
Line 4:		Line 4:

	There is a more formal checklist available [https://github.com/joomla/joomla-cms/blob/4.1-dev/build/release-checklist.md on GitHub] for release leads to use that is intended to complement the steps described in this page.		There is a more formal checklist available [https://github.com/joomla/joomla-cms/blob/4.1-dev/build/release-checklist.md on GitHub] for release leads to use that is intended to complement the steps described in this page.

			Release Leads will need access to a number of resources. But accounts on Github (and being added to [https://github.com/orgs/joomla/teams/cms-release-leads/members the CMS Release Leads team] - which also provides jenkins access), the Forum and Glip are effectively mandatory.

	= CMS Release Cycle =		= CMS Release Cycle =

Wilsonge at 01:04, 30 January 2022

2022-01-30T01:04:00Z

← Older revision		Revision as of 01:04, 30 January 2022
Line 22:		Line 22:
	* <tt>3.10-dev</tt> should be merged into <tt>4.0-dev</tt>		* <tt>3.10-dev</tt> should be merged into <tt>4.0-dev</tt>
	* <tt>4.0-dev</tt> should be merged to <tt>4.1-dev</tt>		* <tt>4.0-dev</tt> should be merged to <tt>4.1-dev</tt>
			* <tt>4.1-dev</tt> should be merged to <tt>4.2-dev</tt>

	It is suggested that at least once per week branch merging occurs.		It is suggested that at least once per week branch merging occurs.

Wilsonge at 01:03, 30 January 2022

2022-01-30T01:03:29Z

← Older revision		Revision as of 01:03, 30 January 2022
Line 1:		Line 1:
	{{RightTOC}}		{{RightTOC}}

	This is a general ~~checklist~~ for managing releases of Joomla! and the Joomla! Framework. This list is best suited for a [[Minor Release]] or [[Maintenance Release]], however the steps will generally apply to a [[Major Release]] as well but will require some judgement calls from the release manager and/or leadership team.		This is a general procedure explanation for managing releases of Joomla! and the Joomla! Framework. This list is best suited for a [[Minor Release]] or [[Maintenance Release]], however the steps will generally apply to a [[Major Release]] as well but will require some judgement calls from the release manager and/or leadership team.

			There is a more formal checklist available [https://github.com/joomla/joomla-cms/blob/4.1-dev/build/release-checklist.md on GitHub] for release leads to use that is intended to complement the steps described in this page.

	= CMS Release Cycle =		= CMS Release Cycle =