rahix/openflexure-microscope-server
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Apply suggestions from code review of branch release-checklist-update

Browse source 
Co-authored-by: Beth Probert <beth_probert@outlook.com>
This commit is contained in:
Julian Stirling 2026-02-19 11:29:50 +00:00
parent 3eb54fefe2
commit c150c07b83
1 changed files with 2 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

4
.gitlab/issue_templates/Release checklist.md
View file

@ -39,13 +39,13 @@ This phase focuses on planning the release and, crucially, getting any major inf
**Branching Note:** During alpha and beta development, feature freeze marks the point where only bug fixes and release preparation may be merged into the default branch. **Branching Note:** During alpha and beta development, feature freeze marks the point where only bug fixes and release preparation may be merged into the default branch.
* [ ] * **Announce:** Announce the Feature Freeze deadline one week out. This should be announced on the OpenFlexure Forum and in a message/email to the core team. * [ ] **Announce:** Announce the Feature Freeze deadline one week out. This should be announced on the OpenFlexure Forum and in a message/email to the core team.
* [ ] **Deadline:** **FEATURE FREEZE**. All MRs for the milestone must be merged. * [ ] **Deadline:** **FEATURE FREEZE**. All MRs for the milestone must be merged.
* [ ] **Deadline:** **UPSTREAM RELEASES**. Any of our repos/packages upstream of the OS and server should have a defined release, for this release to target. * [ ] **Deadline:** **UPSTREAM RELEASES**. Any of our repos/packages upstream of the OS and server should have a defined release, for this release to target.
* [ ] Stitching Released * [ ] Stitching Released
* [ ] Final OS changes merged * [ ] Final OS changes merged
* [ ] **Communication:** Inform the team that all new feature work should target the *next* milestone. * [ ] **Communication:** Inform the team that all new feature work should target the *next* milestone.
* [ ] **Final Server Repo Commit:** Create a (hopefully) final commit to the server before building the OS with the new version and updated changelog. * [ ] **Final Server Repo Commit:** Create a (hopefully) final commit to the server before building the OS with the new version and updated changelog. This commit should include the following:
* [ ] Update version string in: * [ ] Update version string in:
* [ ] `pyproject.toml` * [ ] `pyproject.toml`
* [ ] `test_version_strings.py` * [ ] `test_version_strings.py`