Difference between revisions of "Pre and Post Release To Do"
Jump to navigation
Jump to search
(Fix typo) |
|||
| (38 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
When we prepare for a new release a few things need to be sorted: | When we prepare for a new release a few things need to be sorted: | ||
| + | |||
| + | == Pre Pre-Release == | ||
| + | * Check our meta-qt6, meta-openembedded and openembedded-core layers in testing https://github.com/webOS-ports/webos-ports-setup/blob/testing/conf/layers.txt so that we have tested any security fixes/critical updates before preparing for the release. | ||
== Pre-Release == | == Pre-Release == | ||
| − | * Send out a feature freeze announcement to [email protected] one week before the release | + | * Send out a feature freeze announcement to [email protected] one week before the release (not doing currently to allow for more agile release cycle). |
| − | * Make sure the change log is updated with all the changes for the release: https://github.com/webOS-ports/changelog/blob/master/manifest.json | + | * Update https://github.com/webOS-ports/webos-ports-setup/blob/stable/conf/layers.txt with latest revisions from meta-webos-ports (kirkstone) and meta-smartphone (kirkstone) (Commit message: meta-smartfone,meta-webos-ports: upgrade to latest revisions). |
| − | * Make sure to update the individual device templates to reflect the supported version for this device (device_wop_versions_supported) for [http://webos-ports.org/index.php?title=Template:Device_Mako&action=edit Mako], [http://webos-ports.org/index.php?title=Template:Device_Tenderloin&action=edit Tenderloin] and the [http://webos-ports.org/index.php?title=Template:Device_qemux86&action=edit | + | * Make sure the change log is updated with all the changes for the release: https://github.com/webOS-ports/changelog/blob/master/manifest.json also make sure to bump "platformVersion" and verify the JSON validity on http://www.jsonlint.com |
| − | + | <s> | |
| + | * Trigger http://jenkins.nas-admin.org/job/LuneOS/job/luneos-stable_build-all/ | ||
| + | </s> | ||
| + | * Test the images to make sure they're no release blockers, update the [https://webos-ports.org/wiki/Device_Status Device Status]page. | ||
| + | <s> | ||
| + | * Update the issue tracker, create a new release: http://issues.webos-ports.org/projects/ports/settings should run from 1st till last of month normally. See other months for more info. | ||
| + | * Update any issues assigned to current release to a future release so we don't have anything outstanding against the current release. http://issues.webos-ports.org/projects/ports/roadmap | ||
| + | * Run http://jenkins.nas-admin.org/job/LuneOS/job/luneos-stable_feeds-new-staging/ (this should finish within a few minutes, check the output for the new stage number) | ||
| + | * Run http://jenkins.nas-admin.org/job/LuneOS/job/luneos-stable_feeds-sync-to-public/ and make sure to put the (new stage number -1) from above in the FEED_NUMBERS parameter (Make sure to include the leading 0 so 036 for example). Wait for it to finish. | ||
| + | * Run http://jenkins.nas-admin.org/job/LuneOS/job/luneos-stable_release/ with the same FEED_NUMBER parameter as above, release short name (i.e. crema) and name of unsupported devices (maguro and grouper currently, separated by a space)</s> | ||
| + | * Make sure to update the individual device templates to reflect the supported version for this device (device_wop_versions_supported) for [http://webos-ports.org/index.php?title=Template:Device_Hammerhead&action=edit Hammerhead], [http://webos-ports.org/index.php?title=Template:Device_Mako&action=edit Mako], [http://webos-ports.org/index.php?title=Template:Device_Tenderloin&action=edit Tenderloin], [http://webos-ports.org/index.php?title=Template:Device_Tissot&action=edit Tissot] and the emulator [http://webos-ports.org/index.php?title=Template:Device_qemux86&action=edit Qemux86]. All the release names are already in there, so you just need to move the <!-- to the right so the new release will show :) Also make sure to update the device_last_wop_branch_supported with the release short name (this is used for the directory names) (Herrie) | ||
== Release == | == Release == | ||
| + | |||
| + | * Make sure to add a tag with the release name (e.g. "doppio") as well as date, staging number, release name (e.g. "2018-11-21-053-doppio") in webos-ports-setup repository (pointing to latest stable commit). https://github.com/webOS-ports/webos-ports-setup/releases | ||
== After a release == | == After a release == | ||
| − | * Update https://github.com/webOS-ports/meta-webos-ports/blob/ | + | * Update https://github.com/webOS-ports/meta-webos-ports/blob/kirkstone/meta-luneos/conf/distro/include/luneos.inc to reflect the correct "WEBOS_DISTRO_VERSION_CODENAME" for the next release. (We update current Yocto version in use (kirkstone) and JaMa will cherry pick this to master and other branches if needed. |
Latest revision as of 06:01, 14 February 2024
When we prepare for a new release a few things need to be sorted:
Pre Pre-Release
- Check our meta-qt6, meta-openembedded and openembedded-core layers in testing https://github.com/webOS-ports/webos-ports-setup/blob/testing/conf/layers.txt so that we have tested any security fixes/critical updates before preparing for the release.
Pre-Release
- Send out a feature freeze announcement to [email protected] one week before the release (not doing currently to allow for more agile release cycle).
- Update https://github.com/webOS-ports/webos-ports-setup/blob/stable/conf/layers.txt with latest revisions from meta-webos-ports (kirkstone) and meta-smartphone (kirkstone) (Commit message: meta-smartfone,meta-webos-ports: upgrade to latest revisions).
- Make sure the change log is updated with all the changes for the release: https://github.com/webOS-ports/changelog/blob/master/manifest.json also make sure to bump "platformVersion" and verify the JSON validity on http://www.jsonlint.com
- Test the images to make sure they're no release blockers, update the Device Statuspage.
- Update the issue tracker, create a new release: http://issues.webos-ports.org/projects/ports/settings should run from 1st till last of month normally. See other months for more info.
- Update any issues assigned to current release to a future release so we don't have anything outstanding against the current release. http://issues.webos-ports.org/projects/ports/roadmap
- Run http://jenkins.nas-admin.org/job/LuneOS/job/luneos-stable_feeds-new-staging/ (this should finish within a few minutes, check the output for the new stage number)
- Run http://jenkins.nas-admin.org/job/LuneOS/job/luneos-stable_feeds-sync-to-public/ and make sure to put the (new stage number -1) from above in the FEED_NUMBERS parameter (Make sure to include the leading 0 so 036 for example). Wait for it to finish.
Run http://jenkins.nas-admin.org/job/LuneOS/job/luneos-stable_release/ with the same FEED_NUMBER parameter as above, release short name (i.e. crema) and name of unsupported devices (maguro and grouper currently, separated by a space)- Make sure to update the individual device templates to reflect the supported version for this device (device_wop_versions_supported) for Hammerhead, Mako, Tenderloin, Tissot and the emulator Qemux86. All the release names are already in there, so you just need to move the <!-- to the right so the new release will show :) Also make sure to update the device_last_wop_branch_supported with the release short name (this is used for the directory names) (Herrie)
Release
- Make sure to add a tag with the release name (e.g. "doppio") as well as date, staging number, release name (e.g. "2018-11-21-053-doppio") in webos-ports-setup repository (pointing to latest stable commit). https://github.com/webOS-ports/webos-ports-setup/releases
After a release
- Update https://github.com/webOS-ports/meta-webos-ports/blob/kirkstone/meta-luneos/conf/distro/include/luneos.inc to reflect the correct "WEBOS_DISTRO_VERSION_CODENAME" for the next release. (We update current Yocto version in use (kirkstone) and JaMa will cherry pick this to master and other branches if needed.