Skip to content

docs: add release captain task to copy issues to new board #593

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

Merged
merged 1 commit into from
Apr 30, 2025
Merged

docs: add release captain task to copy issues to new board #593

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
4 changes: 3 additions & 1 deletion wg-releases/release-captain-overview.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,10 +31,12 @@ If you're not able to be the Release Captain during a specific period, or need o
### Start of Shift (Week 1)

* Clone the [project board][] (select "Draft issues will be copied if selected" checkmark)
* ask an admin to make the board public
* Ask an admin to make the board public
* Update all items in the "beta prep" and "stable prep" columns
* This includes updating due dates, and adding any new items
* Make sure that the Releases WG Google Calendar is up to date with Stable & Beta dates
* Copy important issues from the previous two project boards to the new [project board][]
* Review unsorted issues from the (closed) [project board][] two releases prior to the new pre-release board

### Beta Prep (Week 3-4)

Expand Down