Update release_plan.md #20351
Merged
Update release_plan.md #20351
Conversation
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
eleanorjboyd
commented
Dec 9, 2022
| ##### Bump the version of `main` to be a release candidate (also updating debugpy dependences, third party notices, and package-lock.json).❄️ | ||
|
|
||
| - [ ] `git fetch` to ensure you are up to date with `main` on your local machine. | ||
| - [ ] Create a new branch called **`bump-release-[YYYY.minor]`**. |
There was a problem hiding this comment.
added in a naming scheme for all branches one creates to hopefully clarify their functionality and lifespan. Open to suggestions on the naming conventions so plz let me know if you think of something better.
.github/release_plan.md
Outdated
| - [ ] Begin drafting a [blog](http://aka.ms/pythonblog) post. Contact the PM team for this. | ||
| NOTE: Third Party Notices are automatically added by our build pipelines using https://tools.opensource.microsoft.com/notice. | ||
|
|
||
| ### Step 1: |
There was a problem hiding this comment.
broke the doc down into these "steps" which I thought provided more separation between the different actions taken then the previous format but let me know if this makes it more confusing.
|
|
||
| NOTE: this PR should be passing CI and will return `main` to passing CI from step 1. | ||
|
|
||
| ### Step 5: Notifications and Checks on External Release Factors |
There was a problem hiding this comment.
Had trouble naming this step- very open to suggestions
paulacamargo25
previously approved these changes
Dec 13, 2022
brettcannon
requested changes
Dec 13, 2022
Co-authored-by: Brett Cannon <brcan@microsoft.com>
karrtikr
reviewed
Dec 14, 2022
Co-authored-by: Kartik Raj <karraj@microsoft.com>
brettcannon
previously approved these changes
Dec 15, 2022
Co-authored-by: Brett Cannon <brcan@microsoft.com>
karrtikr
reviewed
Dec 16, 2022
Co-authored-by: Kartik Raj <karraj@microsoft.com>
karrtikr
approved these changes
Dec 16, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Hello! I went through and made edits to try and help clarify the release process and all the different branches and PRs that we are creating/keeping track of. I wrote it in a way that makes the most sense to me but please let me know where it is confusing for you.
@paulacamargo25 could you review this first, make edits, and then add @brettcannon as a reviewer?
Thanks!