🔖 Test, complete and release the PresetOnboarding 0.1
Release PresetOnboarding 0.1
Summary
Should be closed when all the following tasks are resolved:
Issue | Merge request | Name | Status |
---|---|---|---|
#38 (closed) |
|
~"On hold" | |
#39 (closed) | !19 (merged), !114 |
|
~"Ready to test" |
#33 (closed) | !19 (merged) | When an option is selected, it shouldn't be selectable in the other configuration panels | ~"Ready to test" |
#31 (closed) | !11 (merged), !18 (merged) | Implement the application cycles in an Enum instead of UI states | ~"Ready to test" |
#27 (closed) | !20 (merged) |
|
~"Ready to test" |
#26 (closed) | !8 (merged), !12 (merged), !15 (merged) |
|
~"Ready to test" |
#11 (closed) | !19 (merged) |
|
~"Ready to test" |
Checklists
All tasks are documented in the release handbook.
Requirements
-
Create a milestone <project> <version>
-
Tag all issues planned for this release -
Create an issue with a release overview
Starting
Updating
-
Rebase candidate branch onto develop
-
Update all files: -
CHANGELOG.md -
AUTHORS.md -
README.md
-
-
Update the software version in -
package.json -
README.md
-
-
Make announcement in the QA channel with the information: -
All added fixes and features -
A link to this issue with an updated overview
-
Ending
-
Update all files: -
CHANGELOG.md -
AUTHORS.md -
README.md
-
-
Update the software version in -
package.json -
README.md
-
-
Merge the MR from the candidate branch to master
ormain
-
Tag the production branch with -
the current version -
the last CHANGELOG
-
-
Create a merge request from master
todevelop
-
Merge back every change
-
-
Close the milestone and this issue
Edited by Valentin Laurent