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

Update release plan to document what to do with main during endgame week #21743

Merged
merged 3 commits into from
Aug 3, 2023
Merged

Update release plan to document what to do with main during endgame week #21743

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
6503ba2
Call out announcing when `main` is (un)locked from endgame week
brettcannon Aug 2, 2023
c2b70bd
Fix a spelling mistake
brettcannon Aug 3, 2023
a24ed2f
Merge branch 'main' into main-during-endgame
brettcannon Aug 3, 2023
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
3 changes: 2 additions & 1 deletion .github/release_plan.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
All dates should align with VS Code's [iteration](https://github.com/microsoft/vscode/labels/iteration-plan) and [endgame](https://github.com/microsoft/vscode/labels/endgame-plan) plans.

Feature freeze is Monday @ 17:00 America/Vancouver, XXX XX.
Feature freeze is Monday @ 17:00 America/Vancouver, XXX XX. At that point, commits to `main` should only be in response to bugs found during endgame testing until the release candidate is ready.


NOTE: the number of this release is in the issue title and can be substituted in wherever you see [YYYY.minor].
Expand Down Expand Up @@ -51,6 +51,7 @@ NOTE: this PR should make all CI relating to `main` be passing again (such as th
- [ ] Manually add/fix any 3rd-party licenses as appropriate based on what the internal build pipeline detects.
- [ ] Open appropriate [documentation issues](https://github.com/microsoft/vscode-docs/issues?q=is%3Aissue+is%3Aopen+label%3Apython).
- [ ] Contact the PM team to begin drafting a blog post.
- [ ] Announce to the development team that `main` is open again.


# Release (Wednesday, XXX XX)
Expand Down