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

Bump package.json version and update release plan #9190

Merged
merged 2 commits into from
Mar 2, 2022
Merged

Bump package.json version and update release plan #9190

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d644d4c
Bump package.json version
DonJayamanne Mar 2, 2022
cc68ba9
Misc
DonJayamanne Mar 2, 2022
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
11 changes: 6 additions & 5 deletions .github/release_plan.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,6 +23,12 @@
- [ ] If there are `release` branches that are two versions old (e.g. release-2020.[current month - 2]) you can delete them at this time (you would have to un-protect the release branches temporarily to delete them).
- [ ] Update `main` after creating the release branch. (Warning: this should happen right after creating the release branch. If this is deferred till later, the `main` and `release` branches can diverge significantly, which may cause merge conflicts.)
- [ ] Merge the changes from release (Changelog, delete news, ThirdPartyNotices) into `main` branch
- [ ] Bump the version number to the next monthly ("YYYY.M.100") release in the `main` branch
- If latest is `2022.2.100`, them bump it to `2022.3.100`,
- This ensures the new new pre-release targets the next version.
- [ ] `package.json`
- [ ] `package-lock.json`
- [ ] Confirm the 3rd part of the version ends with `100`.
- [ ] Create a pull request against `main`
- [ ] Merge pull request into `main`
- [ ] GDPR bookkeeping (@greazer) (🤖; Notes in OneNote under Python VS Code -> Dev Process -> GDPR)
Expand Down Expand Up @@ -69,11 +75,6 @@
* If released version is `YYYY.MM.110`, then hot fix will be `YYYY.MM.120`

# Day of VS Code publishing (Wednesday, XXX XX)
- [ ] Update `main` after the next insider version is made available.
- [ ] Bump the version number to the next monthly ("YYYY.M.100") release in the `main` branch
- [ ] `package.json`
- [ ] `package-lock.json`
- [ ] Confirm the 3rd part of the version ends with `100`.
- [ ] Go through [`info needed` issues](https://github.com/Microsoft/vscode-jupyter/issues?q=is%3Aopen+sort%3Aupdated-asc+label%3Ainfo-needed) and close any that have no activity for over a month (🤖)
- [ ] GDPR bookkeeping (🤖) ((@greazer does regular classification every Monday evening))
- [ ] If any steps were unclear or changed in this release plan please update the `release_plan.md` file to make it clear for the next release
Expand Down
2 changes: 1 addition & 1 deletion package-lock.json
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
{
"name": "jupyter",
"displayName": "Jupyter",
"version": "2022.2.101",
"version": "2022.3.100",
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See comments in releaseplan

"description": "Jupyter notebook support, interactive programming and computing that supports Intellisense, debugging and more.",
"publisher": "ms-toolsai",
"author": {
Expand Down