User:Tracy Graydon/Release Process - Revision history

Tracy Graydon: Tracy Graydon moved page User:Tracy Graydon/Release Documentation on YoctoProject.org to User:Tracy Graydon/Release Process

2017-05-03T07:44:27Z

Tracy Graydon moved page User:Tracy Graydon/Release Documentation on YoctoProject.org to User:Tracy Graydon/Release Process

← Older revision	Revision as of 07:44, 3 May 2017
(No difference)

Tracy Graydon: /* YoctoProject.org Pages */

2017-05-03T07:42:49Z

YoctoProject.org Pages

@@ Line 137: / Line 137: @@
 == YoctoProject.org Pages ==
-<stuff>
+:<stuff>
-<do this, do that>
+:<do this, do that>
-<It wasn't my idea, don't blame me>
+:<It wasn't my idea, don't blame me>
-<how to add the taxonomy/structure for the new release>
+:<how to add the taxonomy/structure for the new release>
-<list of docs to clone>
+:<list of docs to clone>
-<list of pages to clone>
+:<list of pages to clone>
-<invoke the Release Matrix>
+:<invoke the Release Matrix>
-<unpublished to published when going live>
+:<unpublished to published when going live>
-<release notes come back to haunt us>
+:<release notes come back to haunt us>

Tracy Graydon: /* General Process */

2017-05-03T07:35:30Z

General Process

← Older revision		Revision as of 07:35, 3 May 2017
Line 131:		Line 131:

	* Run the relnotes.py script		* Run the relnotes.py script
	<actual example>		:<actual example>
	<comments about revisions to use>		:<comments about revisions to use>
	<what to do with it>		:<what to do with it>
	~~:Actual example~~
	~~: '''OpenEmbedded''': The build system architecture promoted by the Yocto Project.~~
	~~: '''BitBake''': A tool that reads metadata and runs tasks.~~
	~~: '''OpenEmbedded-Core''': The common base set of metadata that BitBake uses. This metadata is shared between OpenEmbedded and the Yocto Project.~~
	~~: '''Poky''': A reference distribution used for test and release purposes by the Yocto Project.~~

	== YoctoProject.org Pages ==		== YoctoProject.org Pages ==

Tracy Graydon: /* General Process */

2017-05-03T07:34:57Z

General Process

← Older revision		Revision as of 07:34, 3 May 2017
Line 134:		Line 134:
	<comments about revisions to use>		<comments about revisions to use>
	<what to do with it>		<what to do with it>
			:Actual example
			: '''OpenEmbedded''': The build system architecture promoted by the Yocto Project.
			: '''BitBake''': A tool that reads metadata and runs tasks.
			: '''OpenEmbedded-Core''': The common base set of metadata that BitBake uses. This metadata is shared between OpenEmbedded and the Yocto Project.
			: '''Poky''': A reference distribution used for test and release purposes by the Yocto Project.

	== YoctoProject.org Pages ==		== YoctoProject.org Pages ==

Tracy Graydon: /* Staging the YoctoProject.org Pages */

2017-05-03T07:32:34Z

Staging the YoctoProject.org Pages

← Older revision		Revision as of 07:32, 3 May 2017
Line 135:		Line 135:
	<what to do with it>		<what to do with it>

	==~~= Staging the~~ YoctoProject.org Pages ===		== YoctoProject.org Pages ==

			<stuff>
			<do this, do that>
			<It wasn't my idea, don't blame me>
			<how to add the taxonomy/structure for the new release>
			<list of docs to clone>
			<list of pages to clone>
			<invoke the Release Matrix>
			<unpublished to published when going live>
			<release notes come back to haunt us>

Tracy Graydon: /* General Process */

2017-05-03T07:29:35Z

General Process

← Older revision		Revision as of 07:29, 3 May 2017
Line 127:		Line 127:
	If staging a Major or Minor release (2.0, 2.3, etc.) release notes will come to you from on high, via Paul Eggleton.		If staging a Major or Minor release (2.0, 2.3, etc.) release notes will come to you from on high, via Paul Eggleton.

	If this is a point release (i.e. 2.2.1 or 2.3.1, etc) you will need to run the relnotes.py script to generate the release notes template and send it as a draft to the CCB ~~group~~ and any other relevant contributors. Known Issues get added, corrections made, etc., or not, and the release notes are finalized.		If this is a point release (i.e. 2.2.1 or 2.3.1, etc) you will need to run the relnotes.py script to generate the release notes template and send it as a draft to the CCB list and any other relevant contributors. Known Issues get added, corrections made, etc., or not, and the release notes are finalized.

Tracy Graydon: /* Release Notes */

2017-05-03T07:28:44Z

Release Notes

← Older revision		Revision as of 07:28, 3 May 2017
Line 121:		Line 121:
	After copying over the content of the RC directory to the staging directory, a good deal of clean up occurs. This involves such things as deleting files we do not publish with releases, removing duplicate files, and converting symlinks to actual files. All of which is very time consuming.		After copying over the content of the RC directory to the staging directory, a good deal of clean up occurs. This involves such things as deleting files we do not publish with releases, removing duplicate files, and converting symlinks to actual files. All of which is very time consuming.

	=== Release Notes ===		== Release Notes ==

	===== General Process =====		===== General Process =====

Tracy Graydon: /* Stage the All the Things */

2017-05-03T07:28:22Z

Stage the All the Things

← Older revision		Revision as of 07:28, 3 May 2017
Line 117:		Line 117:
	Not kidding. This takes many, many hours. The release script first makes a copy of the RC directory, where all work takes place. We do NOT touch the RC directory AT ALL. It will make you cry if you have to try to restore something that gets hosed in there. Seriously. Don't touch it.		Not kidding. This takes many, many hours. The release script first makes a copy of the RC directory, where all work takes place. We do NOT touch the RC directory AT ALL. It will make you cry if you have to try to restore something that gets hosed in there. Seriously. Don't touch it.

	The staging directory will have the same name, sans the ".rc<#>" portion. In this example, the staging directory will be created in the same top level dir as the candidate, and be called "yocto-2.3." i.e. https://autobuilder.yoctoproject.org/pub/releases/yocto-2.3/ Note this link may or may not exist at the time of reading. We clean up old staging directories once releases are published and we know all is well. It is intended for an example only.		The staging directory will have the same name, sans the ".rc<#>" portion. In this example, the staging directory will be created in the same top level dir as the candidate, and be called "yocto-2.3." i.e. https://autobuilder.yoctoproject.org/pub/releases/yocto-2.3/ Note this link may or may not exist at the time of reading. We clean up old staging and RC directories once releases are published and we know all is well. It is intended for an example only.

	After copying over the content of the RC directory to the staging directory, a good deal of clean up occurs. This involves such things as deleting files we do not publish with releases, removing duplicate files, and converting symlinks to actual files. All of which is very time consuming.		After copying over the content of the RC directory to the staging directory, a good deal of clean up occurs. This involves such things as deleting files we do not publish with releases, removing duplicate files, and converting symlinks to actual files. All of which is very time consuming.

Tracy Graydon: /* Stage the All the Things */

2017-05-03T07:27:19Z

Stage the All the Things

← Older revision		Revision as of 07:27, 3 May 2017
Line 101:		Line 101:
	I will use yocto-2.3.rc4 as an example in the steps that follow. Note that all release candidates will end with ".rc<#>". This is a Minor release, whose codename is Pyro and Poky version is 17.0.0.		I will use yocto-2.3.rc4 as an example in the steps that follow. Note that all release candidates will end with ".rc<#>". This is a Minor release, whose codename is Pyro and Poky version is 17.0.0.

	=== Stage the All the Things ===		==== Stage the All the Things ====

	* ssh into your chosen system		* ssh into your chosen system
Line 119:		Line 119:
	The staging directory will have the same name, sans the ".rc<#>" portion. In this example, the staging directory will be created in the same top level dir as the candidate, and be called "yocto-2.3." i.e. https://autobuilder.yoctoproject.org/pub/releases/yocto-2.3/ Note this link may or may not exist at the time of reading. We clean up old staging directories once releases are published and we know all is well. It is intended for an example only.		The staging directory will have the same name, sans the ".rc<#>" portion. In this example, the staging directory will be created in the same top level dir as the candidate, and be called "yocto-2.3." i.e. https://autobuilder.yoctoproject.org/pub/releases/yocto-2.3/ Note this link may or may not exist at the time of reading. We clean up old staging directories once releases are published and we know all is well. It is intended for an example only.

	After copying over the content of the RC directory to the staging directory, a good deal of clean up occurs. This involves such things as deleting files we do not publish with releases, removing duplicate files, and converting symlinks to actual files. All of which is very time consuming.		After copying over the content of the RC directory to the staging directory, a good deal of clean up occurs. This involves such things as deleting files we do not publish with releases, removing duplicate files, and converting symlinks to actual files. All of which is very time consuming.

	=== Release Notes ===		=== Release Notes ===

Tracy Graydon: /* General Process */

2017-05-03T07:26:59Z

General Process

← Older revision		Revision as of 07:26, 3 May 2017
Line 123:		Line 123:
	=== Release Notes ===		=== Release Notes ===

	==== General Process ====		===== General Process =====

	If staging a Major or Minor release (2.0, 2.3, etc.) release notes will come to you from on high, via Paul Eggleton.		If staging a Major or Minor release (2.0, 2.3, etc.) release notes will come to you from on high, via Paul Eggleton.