Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document Space ROS release process #25

Merged
merged 1 commit into from
May 1, 2024
Merged

Document Space ROS release process #25

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions source/How-To-Guides.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,3 +16,4 @@ They contain succinct steps to help you accomplish important tasks quickly.
How-To-Guides/Use-VSCode-With-Docker
How-To-Guides/Use-The-Dashboard
How-To-Guides/Use-Simulation-Assets
How-To-Guides/Releasing-Space-ROS
32 changes: 32 additions & 0 deletions source/How-To-Guides/Releasing-Space-ROS.rst
View file
Open in desktop
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
Loading