Third Party BSP Release Process - Revision history

Eflanagan: /* Overview */

2014-07-01T22:15:23Z

Overview

← Older revision		Revision as of 22:15, 1 July 2014
Line 14:		Line 14:
	* Please do NOT mix major releases (e.g. building a meta-foo bsp layer with edison 6.0 and meta-qt3 5.0.1 ).		* Please do NOT mix major releases (e.g. building a meta-foo bsp layer with edison 6.0 and meta-qt3 5.0.1 ).
	* Please ensure that your release is built with a known poky release.		* Please ensure that your release is built with a known poky release.
			* While you can include the poky release with your BSP, it is STRONGLY suggested that you do not, but rather provide a link to it. See [[BKM:_Packaging_a_BSP_for_Release]]

	===Release Checklist===		===Release Checklist===
Line 34:		Line 35:
	* Download links are made live and verified by both the Yocto Release Engineer and You.		* Download links are made live and verified by both the Yocto Release Engineer and You.
	* If you would like the release announcement to be sent out to yocto-announce you have provided the text to the Yocto Community Manager (Jefro) and the Yocto Release Engineer.		* If you would like the release announcement to be sent out to yocto-announce you have provided the text to the Yocto Community Manager (Jefro) and the Yocto Release Engineer.

			===Release Checklist===

Darknighte: Updating broken link

2014-06-10T21:32:00Z

Updating broken link

← Older revision		Revision as of 21:32, 10 June 2014
Line 4:		Line 4:

	===Release Requirements===		===Release Requirements===
	* If your DL_DIR contains source which we are required to provide and that source package/revision does not exist at http://downloads.yoctoproject.org/sources you MUST provide the source, as generated from your DL_DIR.		* If your DL_DIR contains source which we are required to provide and that source package/revision does not exist at http://downloads.yoctoproject.org/mirror/sources/ you MUST provide the source, as generated from your DL_DIR.
	* md5sums must be generated for EVERY file to be included in the release. Please use something similar to <code> find . -type f -exec md5sum {} \; >> ../mybsp-poky-edison-6.0.md5sum </code> to generate.		* md5sums must be generated for EVERY file to be included in the release. Please use something similar to <code> find . -type f -exec md5sum {} \; >> ../mybsp-poky-edison-6.0.md5sum </code> to generate.
	** This should include additional files needed from your DL_DIR.		** This should include additional files needed from your DL_DIR.

Eflanagan: /* Release Requirements */

2013-05-20T18:09:31Z

Release Requirements

← Older revision		Revision as of 18:09, 20 May 2013
Line 13:		Line 13:
	* Everything required for release must available to the Yocto Release Engineer at least 48 hours prior to release. This time is needed for mirror propagation.		* Everything required for release must available to the Yocto Release Engineer at least 48 hours prior to release. This time is needed for mirror propagation.
	* Please do NOT mix major releases (e.g. building a meta-foo bsp layer with edison 6.0 and meta-qt3 5.0.1 ).		* Please do NOT mix major releases (e.g. building a meta-foo bsp layer with edison 6.0 and meta-qt3 5.0.1 ).
			* Please ensure that your release is built with a known poky release.

	===Release Checklist===		===Release Checklist===

Eflanagan: /* Release Requirements */

2013-04-18T18:46:38Z

Release Requirements

← Older revision		Revision as of 18:46, 18 April 2013
Line 4:		Line 4:

	===Release Requirements===		===Release Requirements===
	* If your DL_DIR contains source which we are required to provide and that source package/revision does not exist at http://downloads.yoctoproject.org/sources you MUST provide the ~~package~~.		* If your DL_DIR contains source which we are required to provide and that source package/revision does not exist at http://downloads.yoctoproject.org/sources you MUST provide the source, as generated from your DL_DIR.
	* md5sums must be generated for EVERY file to be included in the release. Please use something similar to <code> find . -type f -exec md5sum {} \; >> ../mybsp-poky-edison-6.0.md5sum </code> to generate.		* md5sums must be generated for EVERY file to be included in the release. Please use something similar to <code> find . -type f -exec md5sum {} \; >> ../mybsp-poky-edison-6.0.md5sum </code> to generate.
	** This should include additional files needed from your DL_DIR.		** This should include additional files needed from your DL_DIR.

Eflanagan: /* Overview */

2012-01-25T03:30:27Z

Overview

← Older revision		Revision as of 03:30, 25 January 2012
Line 1:		Line 1:
	==Overview==		==Overview==

	Third Party BSPs may be ~~releases~~ with any major/minor Yocto release by the maintainers of the various BSP layers. The process for including a BSP release into a yocto release has a few routes, some less complicated than others.		Third Party BSPs may be released with any major/minor Yocto release by the maintainers of the various BSP layers. The process for including a BSP release into a yocto release has a few routes, some less complicated than others.

	===Release Requirements===		===Release Requirements===

Eflanagan: /* Overview */

2011-10-25T21:25:35Z

Overview

← Older revision		Revision as of 21:25, 25 October 2011
Line 6:		Line 6:
	* If your DL_DIR contains source which we are required to provide and that source package/revision does not exist at http://downloads.yoctoproject.org/sources you MUST provide the package.		* If your DL_DIR contains source which we are required to provide and that source package/revision does not exist at http://downloads.yoctoproject.org/sources you MUST provide the package.
	* md5sums must be generated for EVERY file to be included in the release. Please use something similar to <code> find . -type f -exec md5sum {} \; >> ../mybsp-poky-edison-6.0.md5sum </code> to generate.		* md5sums must be generated for EVERY file to be included in the release. Please use something similar to <code> find . -type f -exec md5sum {} \; >> ../mybsp-poky-edison-6.0.md5sum </code> to generate.
	* This should include additional files ~~in sources~~.		** This should include additional files needed from your DL_DIR.
	* I do validate every ~~files~~ prior to release and will not gpg sign an invalid .md5sum		** I do validate every file's md5sum prior to release and will not gpg sign an invalid .md5sum
	* You must include release notes.		* You must include release notes.
	* You should include some sort of QA report, preferably a link to the QA report on the yocto wiki.		* You should include some sort of QA report, preferably a link to the QA report on the yocto wiki.
Line 17:		Line 17:

	2-4 Weeks Prior:		2-4 Weeks Prior:

	* You have emailed the Yocto Release Engineer with your intention to release. Please try to give an estimate size of the release and against what released version of yocto you are building against.		* You have emailed the Yocto Release Engineer with your intention to release. Please try to give an estimate size of the release and against what released version of yocto you are building against.
			<p></p>
	Prior to the Release:		Prior to the Release:
	* You have generated a tested BSP release against a known released version of yocto. Please include the git hash for EVERY official yocto layer you have built against. (meta-qt3, etc).		* You have generated a tested BSP release against a known released version of yocto. Please include the git hash for EVERY official yocto layer you have built against. (meta-qt3, etc).
Line 26:		Line 25:
	* You have validated that all required source files are either in http://downloads.yoctoproject.org/sources or in the area to be used for the release.		* You have validated that all required source files are either in http://downloads.yoctoproject.org/sources or in the area to be used for the release.
	* You have created a valid and documented BSP layer tarball named LAYERNAME-RELEASENAME-M.m.p.tar.bz2		* You have created a valid and documented BSP layer tarball named LAYERNAME-RELEASENAME-M.m.p.tar.bz2
			<p></p>48 Hours Prior to your release:
	48 Hours Prior to your release:
	* You have emailed the Yocto Release Engineer a link to download all files needed for the release		* You have emailed the Yocto Release Engineer a link to download all files needed for the release
			* I validate the md5sums
			* I gpg sign the .md5sum file and prepare the release for the release directory/mirrors
			<p></p>
	Hours Prior to release:		Hours Prior to release:
	* Download links are made live and verified by both the Yocto Release Engineer and You.		* Download links are made live and verified by both the Yocto Release Engineer and You.
	* If you would like the release announcement to be sent out to yocto-announce you have provided the text to the Yocto Community Manager (Jefro) and the Yocto Release Engineer.		* If you would like the release announcement to be sent out to yocto-announce you have provided the text to the Yocto Community Manager (Jefro) and the Yocto Release Engineer.

Eflanagan: Created page with "==Overview== Third Party BSPs may be releases with any major/minor Yocto release by the maintainers of the various BSP layers. The process for including a BSP release into a yoc..."

2011-10-25T21:14:22Z

Created page with "==Overview== Third Party BSPs may be releases with any major/minor Yocto release by the maintainers of the various BSP layers. The process for including a BSP release into a yoc..."

New page

==Overview==

Third Party BSPs may be releases with any major/minor Yocto release by the maintainers of the various BSP layers. The process for including a BSP release into a yocto release has a few routes, some less complicated than others.

===Release Requirements===
* If your DL_DIR contains source which we are required to provide and that source package/revision does not exist at http://downloads.yoctoproject.org/sources you MUST provide the package.
* md5sums must be generated for EVERY file to be included in the release. Please use something similar to <code> find . -type f -exec md5sum {} \; >> ../mybsp-poky-edison-6.0.md5sum </code> to generate.
* This should include additional files in sources.
* I do validate every files prior to release and will not gpg sign an invalid .md5sum
* You must include release notes.
* You should include some sort of QA report, preferably a link to the QA report on the yocto wiki.
* You should inform the Yocto Release Engineer (elizabeth.flanagan@intel.com) at least 2 weeks prior to your intended release date (We prefer 4 weeks so we don't surprise those kind folks who mirror yocto).
* Everything required for release must available to the Yocto Release Engineer at least 48 hours prior to release. This time is needed for mirror propagation.
* Please do NOT mix major releases (e.g. building a meta-foo bsp layer with edison 6.0 and meta-qt3 5.0.1 ).

===Release Checklist===

2-4 Weeks Prior:

* You have emailed the Yocto Release Engineer with your intention to release. Please try to give an estimate size of the release and against what released version of yocto you are building against.

Prior to the Release:
* You have generated a tested BSP release against a known released version of yocto. Please include the git hash for EVERY official yocto layer you have built against. (meta-qt3, etc).
* You have created a publicly accessible QA report that the release may link against.
* You have generated an md5sum file of all files needed.
* You have validated that all required source files are either in http://downloads.yoctoproject.org/sources or in the area to be used for the release.
* You have created a valid and documented BSP layer tarball named LAYERNAME-RELEASENAME-M.m.p.tar.bz2

48 Hours Prior to your release:
* You have emailed the Yocto Release Engineer a link to download all files needed for the release

Hours Prior to release:
* Download links are made live and verified by both the Yocto Release Engineer and You.
* If you would like the release announcement to be sent out to yocto-announce you have provided the text to the Yocto Community Manager (Jefro) and the Yocto Release Engineer.