Skip to content

Write out more explicit steps for cutting a release #388

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 2 commits into from
Dec 11, 2017
Merged

Write out more explicit steps for cutting a release #388

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
271244e
Write out more explicit steps for cutting a release
brettcannon Dec 11, 2017
39965c0
Make sure we actually get the changes from CELA
brettcannon Dec 11, 2017
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
15 changes: 10 additions & 5 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -112,9 +112,13 @@ time-critical as a new feature may be.
* [tock] Begin applying any changes to the development process as
agreed upon during the previous "tick" cycle
* Day 7 (Monday)
* 3rd-party dependencies frozen to give CELA time to update TPN file
* 3rd-party dependencies frozen
* Ask CELA to update the TPN file
* Day 14 (2nd Monday)
* Update the TPN file as instructed by CELA
* Bump version number
* Code freeze
* Cut a `.vsix` file for testing
* Go through
[issues awaiting validation](https://github.com/Microsoft/vscode-python/issues?q=label%3A%22awaiting+4-validation%22+is%3Aclosed)
& validate they have been fixed (and not subsequently broken by
Expand All @@ -123,13 +127,14 @@ time-critical as a new feature may be.
[documentation](https://code.visualstudio.com/docs/python/python-tutorial)
-- including the
[WOW](https://code.visualstudio.com/docs/languages/python) page)
-- is updated appropriately
-- has [appropriate pull requests](https://github.com/microsoft/vscode-docs/pulls)
* Update the
[changelog](https://github.com/Microsoft/vscode-python/blob/master/CHANGELOG.md)
* Write a post for the [team blog](https://aka.ms/pythonblog)
* Upload the new version of
[the extension](https://marketplace.visualstudio.com/items?itemName=ms-python.python)
* Tag the release in git
* Draft a post for the [team blog](https://aka.ms/pythonblog)

Assuming no last-minute issues, the release should be made public
later that same week.

### Issue triaging

Expand Down