-
Notifications
You must be signed in to change notification settings - Fork 11
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
WIP: Document Space ROS release process
- Loading branch information
Showing
2 changed files
with
33 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,32 @@ | ||
Releasing Space ROS | ||
=================== | ||
|
||
Before the release window | ||
------------------------- | ||
|
||
- Determine the release tag of the form rosdist-year.month.point, for example ``humble-2024.01.0`` | ||
- Open a new issue with a title of the form "year-month Release", for example "2024-01 Release" | ||
- Create a milestone that matches the release tag in each repo under the Space ROS organization | ||
- Create a new view in the Space ROS Project filtered by milestone | ||
|
||
During the release window | ||
------------------------- | ||
|
||
- Tag issues intended for the release with the correct milestone | ||
- Update issue status on the project view for the release | ||
|
||
At the end of the release window | ||
-------------------------------- | ||
|
||
- Create release/distro branches on `docker`, `demos`, `simulation`, `docs`, and `process_sarif`. | ||
- Update the .repos files to the new versions for the new distro sync. | ||
- Re-run the tests, creating issues for any that failed. | ||
- Docker images are already built but only tagged `latest`, must tag release as release name. | ||
- Add announcements to Website, Docs, and Discourse | ||
- Create next release milestone and tracking issue | ||
|
||
After release window | ||
-------------------- | ||
|
||
- Open issues based on release experience | ||
- Document lessons learned |