Bug 6683

Summary:	Produce a script to automate release preparation tasks
Product:	[Build System, Metadata & Runtime] OE-Core	Reporter:	Belen Barros Pena <belen.barros.pena>
Component:	core	Assignee:	Unassigned <unassigned>
Status:	RESOLVED OBSOLETE	QA Contact:
Severity:	enhancement
Priority:	Medium	CC:	alexandru.damian, bluelightning, brian.avery, david.reyna, elizabeth.flanagan, meta.mr.watcher, meta.watcher, randy.macleod, tracy.graydon
Version:	unspecified
Target Milestone:	Future
Hardware:	All
OS:	Multiple
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	No (bug/feature does not impact docs)

Description Belen Barros Pena 2014-09-04 17:23:43 UTC

While finalising some Toaster details, Paul Eggleton observed that the list of things that must be done to get ready for release keeps on growing, and that it might be a good idea to automate such tasks so that we don't forget about them. 

We should probably start by putting together a complete lists of those "release preparation" tasks. 

In the case of Toaster, a default configuration file needs to be created that specifies, between other things, the list of releases that Toaster will support out of the box (in the case of 1.7, it will be 1.6 and 1.7).

Comment 1 Alexandru Damian 2014-09-09 10:20:21 UTC

More info about this script.

    - What is it producing?
It produces a file that lives in poky/meta/conf/, named toasterconf.json. A sample of this file (manually coded) is here:

http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=adamian/20140812_toasterconf&id=74bc64d5a18845613bc0e042bcfb35e848ecf686

    - Where is it producing it?
I am not sure - the script runs a "bitbake -e" on the current tree, greps some values, and writes them to poky/meta/conf/toasterconf.json
 
    - Where does it need to be released to?
In the poky source tree.
 
    - What targets does it need to be run on?
It's global configuration, no targets needed.
 
    - Where does it need to be run from?
I am not sure - I think any build/ directory would work.

Comment 2 Beth Flanagan 2014-12-08 19:09:11 UTC

With my upcoming sabbatical, this becomes much more important.

Comment 3 brian avery 2017-06-15 15:26:03 UTC

toaster now uses fixtures to determine which versions are supported as of 2.2. also, which versions are supported are subject to bitbake api breakage across versions, so can not be automatically generated.

This script is therefore unlikely to be useful to toaster at the current time (2.4)

Comment 4 David Reyna 2017-06-27 02:04:27 UTC

With Toaster 2.x and fixtures, the remaining release steps are:
  1) Get the 'secret' name of new release branch 
  2) Get the bitbake release branch number

These values are updated in the fixture XML files before the release is closed.

Given that these are last minute values and are few in number, a release script is no longer very applicable.

I am looking to mark this defect as 'obsolete'.

Comment 5 Randy MacLeod 2020-04-09 15:04:17 UTC

David, Do you still think this is obsolete? If so close it.

Comment 6 David Reyna 2020-04-09 16:04:11 UTC

Closing this as obsolete