Skip to content

Commit 9542545

Browse files
committed
Document Space ROS release process (#24)
1 parent dd8cff4 commit 9542545

File tree

2 files changed

+33
-0
lines changed

2 files changed

+33
-0
lines changed

source/How-To-Guides.rst

+1
Original file line numberDiff line numberDiff line change
@@ -16,3 +16,4 @@ They contain succinct steps to help you accomplish important tasks quickly.
1616
How-To-Guides/Use-VSCode-With-Docker
1717
How-To-Guides/Use-The-Dashboard
1818
How-To-Guides/Use-Simulation-Assets
19+
How-To-Guides/Releasing-Space-ROS
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,32 @@
1+
Releasing Space ROS
2+
===================
3+
4+
Before the release window
5+
-------------------------
6+
7+
- Determine the release tag of the form rosdist-year.month.point, for example ``humble-2024.01.0``
8+
- Open a new issue with a title of the form "year-month Release", for example "2024-01 Release"
9+
- Create a milestone that matches the release tag in each repo under the Space ROS organization
10+
- Create a new view in the Space ROS Project filtered by milestone
11+
12+
During the release window
13+
-------------------------
14+
15+
- Tag issues intended for the release with the correct milestone
16+
- Update issue status on the project view for the release
17+
18+
At the end of the release window
19+
--------------------------------
20+
21+
- Create release/distro branches on `docker`, `demos`, `simulation`, `docs`, and `process_sarif`.
22+
- Update the .repos files to the new versions for the new distro sync.
23+
- Re-run the tests, creating issues for any that failed.
24+
- Docker images are already built but only tagged `latest`, must tag release as release name.
25+
- Add announcements to Website, Docs, and Discourse
26+
- Create next release milestone and tracking issue
27+
28+
After release window
29+
--------------------
30+
31+
- Open issues based on release experience
32+
- Document lessons learned

0 commit comments

Comments
 (0)