kernel-sru-workflow
|
Size: 5424
Comment:
|
Size: 9014
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 27: | Line 27: |
| 1. The kernel team creates a tracking bug created, all tasks will be set to their initial state (status '''Incomplete''') and be assigned to the appropriate team. 1. The kernel team sets the '''Create-upload-and-build-source-package''' task to the in-progress state (status '''In Progress'') 1. The kernel team builds and uploads the source package to the kernel team ppa. Once the source package successfully builds and is ready to be copied to proposed the task state is changed to completed (status '''Fix Released'''). 1. '''Workflow Mgr.''' detects that the state of the '''Create-upload-and-build-source-package''' task has completed and changes the '''Promote-to-proposed''' task to it's ready-to-start state (status '''Confirmed'''). 1. An archive admin sets the '''Promote-to-proposed''' task to in-progress (status: '''In Progress''') and copies the package to the '''proposed''' pocket in the archive. 1. Once the package has been copied an archive admin sets the '''Promote-to-proposed''' task to completed (status: '''Fix Released'''). 1. '''Workflow Mgr.''' detects that the state of the '''Promote-to-proposed''' task is now completed and changes the state of the '''Verification-testing''' task to the ready-to-start state (status: '''Confirmed'''). 1. Once all the bugs, not fixed by stable upstream releases, listed in the changlog have been marked '''verification-done''', the '''Workflow Mgr.''' changes the state of the '''Certification-testing''' and '''Regression-testing''' tasks to the ready-to-start state (status: '''Confirmed'''). 1. When the HW Certification team detects that the '''Certification-testing'' task is in the ready-to-start state (status: '''Confirmed''') and they start testing, they change the tasks state to in-progress (status: '''In Progress'''). 1. When the QA team detects that the '''Regression-testing'' task is in the ready-to-start state (status: '''Confirmed''') and they start testing, they change the tasks state to in-progress (status: '''In Progress'''). 1. Once certification testing completes, the HW certification team changes the state of the '''Certification-testing''' task to completed (status: '''Fix Released'''). 1. Once regression testing completes, the QA test changes the state of the '''Regression-testing''' task to completed (status:'''Fix Released'''). 1. When both the '''Certification-testing''' and '''Regression-testing''' tasks have been set to completed states (status: '''Fix Released''') and both the '''certification-testing-completed-successfully''' and '''regression-testing-completed-successfully''' tags have been added by the appropriate team, the '''Workflow Mgr.''' changes the state of the '''Promote-to-updates''' task to the ready-to-start state (status:'''Confirmed'''). 1. The '''Workflow Mgr.''' detects that a new release tracking bug has been created and sets the current state of the '''Create-and-upload-source-package'''. 1. An archive admin copies the package from '''proposed''' to the '''updates''' pocket in the archive and sets the '''Promote-to-updates''' task as '''Fix Released'''. 1. If there were CVEs and if the '''Promote-to-security''' task is set to '''Confirmed''', the security team takes care of any tasks they deem necessary prior to having an archive admin copy the release to the '''security''' pocket. '''Note:''' Some tasks can move from '''Confirmed''' straight to '''Fix Released''' depending on the amount of time/effort involved in the task. === An example: === |
|
| Line 38: | Line 67: |
| 1. Once all the bugs have been marked '''verification-done''' the '''Workflow Mgr.''' changes the state of '''Certification-testing''' and '''Regression-testing''' to '''Confirmed''' | 1. Once all the bugs, not fixed by stable upstream releases, listed in the changled have been marked '''verification-done''' the '''Workflow Mgr.''' changes the state of '''Certification-testing''' and '''Regression-testing''' to '''Confirmed''' |
| Line 43: | Line 72: |
| 1. Once certification testing completes, the HW certification team changes the state of '''Certification-testing''' to '''Fix Released''' and begins certification testing. 1. Once regression testing completed, the QA test changes the state of '''Regression-testing''' to '''Fix Released''' and begins regression testing. |
1. Once certification testing completes, the HW certification team changes the state of '''Certification-testing''' to '''Fix Released'''. 1. Once regression testing completes, the QA test changes the state of '''Regression-testing''' to '''Fix Released'''. |
| Line 46: | Line 75: |
| 1. '''Workflow Mgr.''' changes the state of '''Promote-to-updates''' to '''Confirmed'''. | 1. When both '''Certification-testing''' and '''Regression-testing''' have been set to '''Fix Released''' the '''Workflow Mgr.''' changes the state of '''Promote-to-updates''' to '''Confirmed'''. |
| Line 49: | Line 78: |
| 1. An archive admin copies the package from '''proposed''' to the '''updates''' and if necessary '''security''' pockets in the archive and sets the '''Promote-to-updates''' and '''Promote-to-security''' tasks as '''Fix Released'''. | 1. An archive admin copies the package from '''proposed''' to the '''updates''' pocket in the archive and sets the '''Promote-to-updates''' task as '''Fix Released'''. |
Kernel SRU Workflow (proposed)
The kernel release tracking bug is going to be changed to facilitate better communication between the responsible parties and clearer handoffs as the release progresses.
We are taking advantage of existing Launchpad capabilities.
When a kernel release tracking bug is created, it is created against the relevant kernel source package and nominated for the related Ubuntu series. The new process will target the bug against an additional project, the "Kernel SRU Workflow" project and nominate it for all the series that are defined for that project.
The "Kernel SRU Workflow" project has a number of custom "series" created for it that represent the different stages of the kernel cadence. A "series" represents a task to be accomplished by a team/person. The different tasks will be assigned to the team/person responsible for that stage. The assignee will set the status of the tasks they are working.
An automated script will run periodicaly to monitor the current state of the different tasks and change status when necessary. This script will be referred to below as the Workflow Mgr. The kernel team will develop this bot.
An example:
The kernel team creates a tracking bug created, all tasks will be set to their initial state (status Incomplete) and be assigned to the appropriate team.
The kernel team sets the Create-upload-and-build-source-package task to the in-progress state (status In Progress)
The kernel team builds and uploads the source package to the kernel team ppa. Once the source package successfully builds and is ready to be copied to proposed the task state is changed to completed (status Fix Released).
Workflow Mgr. detects that the state of the Create-upload-and-build-source-package task has completed and changes the Promote-to-proposed task to it's ready-to-start state (status Confirmed).
An archive admin sets the Promote-to-proposed task to in-progress (status: In Progress) and copies the package to the proposed pocket in the archive.
Once the package has been copied an archive admin sets the Promote-to-proposed task to completed (status: Fix Released).
Workflow Mgr. detects that the state of the Promote-to-proposed task is now completed and changes the state of the Verification-testing task to the ready-to-start state (status: Confirmed).
Once all the bugs, not fixed by stable upstream releases, listed in the changlog have been marked verification-done, the Workflow Mgr. changes the state of the Certification-testing and Regression-testing tasks to the ready-to-start state (status: Confirmed).
When the HW Certification team detects that the Certification-testing task is in the ready-to-start state (status: Confirmed) and they start testing, they change the tasks state to in-progress (status: In Progress).
When the QA team detects that the Regression-testing task is in the ready-to-start state (status: Confirmed) and they start testing, they change the tasks state to in-progress (status: In Progress).
Once certification testing completes, the HW certification team changes the state of the Certification-testing task to completed (status: Fix Released).
Once regression testing completes, the QA test changes the state of the Regression-testing task to completed (status:Fix Released).
When both the Certification-testing and Regression-testing tasks have been set to completed states (status: Fix Released) and both the certification-testing-completed-successfully and regression-testing-completed-successfully tags have been added by the appropriate team, the Workflow Mgr. changes the state of the Promote-to-updates task to the ready-to-start state (status:Confirmed).
The Workflow Mgr. detects that a new release tracking bug has been created and sets the current state of the Create-and-upload-source-package.
An archive admin copies the package from proposed to the updates pocket in the archive and sets the Promote-to-updates task as Fix Released.
If there were CVEs and if the Promote-to-security task is set to Confirmed, the security team takes care of any tasks they deem necessary prior to having an archive admin copy the release to the security pocket.
Note: Some tasks can move from Confirmed straight to Fix Released depending on the amount of time/effort involved in the task.
Tracking bug created, all tasks will be status Kernel team sets the The source package builds successfully and the kernel team sets the An archive admin sets the Once the package has been copied an archive admin sets the Once all the bugs, not fixed by stable upstream releases, listed in the changled have been marked The HW certification team changes the state of The QA test changes the state of Once certification testing completes, the HW certification team changes the state of Once regression testing completes, the QA test changes the state of When both If there were CVEs related to the release, the An archive admin copies the package from If there were CVEs and if the
Series Owner Description Upload-to-ppa Kernel Team The kernel team has uploaded the source package for the release to the kernel team's ppa. Promote-to-proposed Archive Admin Team The package in the kernel team's ppa is copied to the proposed pocket in the archive. Verification-testing Kernel Team The bugs related to the release are being verified as having been fixed by the appropriate community member. Certification-testing HW Certification Team The kernel in proposed is tested via the certification tests. Regression-testing QA Team The kernel in proposed is tested for regressions. Promote-to-updates Archive Admin Team The package is copied from the proposed pocket to the updates pocket in the archive. Promote-to-security Security Team The package is copied from the proposed pocket to the security pocket in the archive.
Status Description Incomplete The initial state of the task. This is not ready for the assigned team/person to begin working on that task. Confirmed The task is ready for the asigned team/person to begin working it. In Progress The assigned team/person has begun the work associated with the given task. Invalid The process state is not appropriate for the given kernel release. Fix Released The assigned team/person has finished the task. An example:
Incomplete and be assigned to the appropriate team. Series
Status
Kernel/kernel-sru-workflow (last edited 2023-12-06 20:01:36 by setuid)