SOF 2.15 Release Checklist

[kv2019i]

Planned Timeline

• May-June Aug-Sep release

Pre-RC1 Steps, Creation of Stable Branch

• Tag features and issue list with milestone https://github.com/thesofproject/sof/milestones/v2.15
• Choose a SOF commit on main branch as candidate for stable branch https://github.com/thesofproject/sof/tree/v2.15-rc1
• Tag branch point as rc1
• Testing & sign off
• Branch stable v2.xx -- depending on main stability can be one week before RC1 or at the same time https://github.com/thesofproject/sof/tree/stable-v2.15
• Move any features in the milestone list that did not make it in time before the stable branch cut-off date, to the next release.
• Update versions.json in mainline
• Update versions.json in stable branch

RC2 Steps:

• Cherry pick critical features and bug fixes to stable-v2.15 for RC2
• Perform FW security scan and fix opens
• Testing & sign off
• Tag v2.15-RC2 -> https://github.com/thesofproject/sof/releases/tag/v2.15-rc2

Final Release Steps:

• Cherry pick critical features and bug fixes to stable-v2.xx
• Testing & sign off
• Tag v2.xx release
• Publish release on https://github.com/thesofproject/sof/releases

Final Release, vendor specific steps / Intel:

• Production sign FW, upload FW and topology binaries to internal release folder
• Publish release on https://github.com/thesofproject/sof-bin/blob/main/HOWTO-new-release.md

Final Release, vendor specific steps / OtherVendor:

• ( add steps here )

Final Steps:

• Move any unfinished issues to next milestone

[github-actions]

This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time.

[lgirdwood]

Pending CI transition. Base FW config will be same as 2.14, new features will be modules and platform support.

[github-actions]

This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time.

[kv2019i]

Updating timeline to Aug-Sep

[dbaluta]

@kv2019i will we aim to align SOF releases with Zephyr releases (like 2 times per year?)

[kv2019i]

@dbaluta wrote:

@kv2019i will we aim to align SOF releases with Zephyr releases (like 2 times per year?)

Yes, that would be the target. AFAIK, no specific cadence has been agreed in the steering group, so we are planning one release at a time, but given the link to Zephyr timeline, it makes most sense to align. So currently that would mean two or one releases per year. One interesting open is is whether we should move to using Zephyr release tags. Personally, I think our current rolling model (= we pick a commit from Zephyr mainline) is still pretty ok. Even with the rolling model, it makes sense to align to Zephyr timeline so that we are not trying to get SOF rc1 together when Zephyr mainline is frozen and not accepting any PRs.

[lgirdwood]

Validation run is starting, if all good we can tag an RC1