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.

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

Release plan for January 2018 #547

Closed
38 tasks done
brettcannon opened this issue Jan 9, 2018 · 3 comments
Closed
38 tasks done

Release plan for January 2018 #547

brettcannon opened this issue Jan 9, 2018 · 3 comments
Assignees

Comments

@brettcannon
Copy link
Member

brettcannon commented Jan 9, 2018

Helpful links & info

Schedule

Tuesday January 09

  • Finalize adding initial set of issues to the milestone
  • Make sure all issues for this milestone are assigned
  • Update pinned versions of dependencies
  • Close all issues awaiting more info that have been inactive for over a month

Monday, January 22

Get legal details started

  • Announce the lock-down of any new dependencies for this release
  • Make sure CELA has been notified of all changes to dependencies

Release a beta version for testing

  • Update the version to be a beta
  • Generate a beta .vsix file
  • Announce the location of the beta .vsix

Prep for feature freeze

  • Schedule bug bash

Monday, January 29

  • Make sure the TPNs have been updated appropriately
  • Land any last-minute pull requests
  • Announce feature freeze

Test the release candidate code

  • Update the version number to be an rc
  • Generate a release candidate .vsix file for testing
  • Announce the location of release candidate.vsix
  • Mark all closed, fixed issues in the milestone as awaiting 4-validation
  • Validate fixed issues

Prep for releasing

  • Get team agreement that the code is ready to be released
  • Gather the names of all external contributors who contributed a pull request to this release
  • Update the changelog
  • Drop the rc suffix from the version number
  • Make sure CI is passing
  • Create the release- branch
  • Generate final .vsix file from the release- branch
  • Make sure the documentation -- including the WOW page -- has appropriate pull requests
  • Begin drafting a blog post

Start preparing for the next release

  • Bump the version number to the next alpha
  • Make sure the next two milestones exist
  • Lift the feature freeze
  • Create a new release plan

Clean up after this release

Sometime after January 29

  • Upload the final .vsix file
  • Publish documentation changes
  • Publish the blog post
  • Create a release on GitHub (which creates the git tag)
@brettcannon brettcannon self-assigned this Jan 9, 2018
@brettcannon
Copy link
Member Author

brettcannon commented Jan 29, 2018

Changelog:

  • Sending a block of code with multiple global-level scopes now works (#259)
  • Automatic activation of virtual or conda environment in terminal when executing Python code/file (#383)
  • Introduce a Python: Create Terminal to create a terminal that activates the selected virtual/conda environment (#622)
  • Add a ko-kr translation (#540)
  • Add a ru translation (#411)
  • Performance improvements to detection of virtual environments in current workspace (#372)
  • Correctly detect 64-bit python (#414)
  • Display parameter information while typing (#70)
  • Use localhost instead of 0.0.0.0 when starting debug servers (#205)
  • Ability to configure host name of debug server (#227)
  • Use environment variable PYTHONPATH defined in .env for intellisense and code navigation (#316)
  • Support path variable when debugging (#436)
  • Ensure virtual environments can be created in .env directory (#435, #482, #486)
  • Reload environment variables from .env without having to restart VS Code (#183)
  • Support debugging of Pyramid framework on Windows (#519)
  • Code snippet for pubd (#545)
  • Code clean up (#353, #352, #354, #456, #491, #228, #549, #594, #617, #556)
  • Move to yarn from npm (#421)
  • Add code coverage for extension itself (#464)
  • Releasing insiders build of the extension and uploading to cloud storage (#429)
  • Japanese translation (#434)
  • Russian translation (#411)
  • Support paths with spaces when generating tags with Build Workspace Symbols (#44)
  • Add ability to configure the linters (#572)
  • Add default set of rules for Pylint (#554)
  • Prompt to install formatter if not available (#524)
  • work around editor.formatOnSave failing when taking more then 750ms (#124, #590, #624, #427, #492)
  • Function argument completion no longer automatically includes the default argument (#522)
  • When sending a selection to the terminal, keep the focus in the editor window (#60)
  • Install packages for non-environment Pythons as --user installs (#527)
  • No longer suggest the system Python install on macOS when running Select Interpreter as it's too outdated (e.g. lacks pip) (#440)
  • Fix potential hang from Intellisense (#423)

@ericsnowcurrently
Copy link
Member

ericsnowcurrently commented Jan 29, 2018

I also marked #477 as validated.

@brettcannon
Copy link
Member Author

I consider the changelog finished. I will pull it into my PR to cut the RC release, so any future changes please let me know and I will update my PR.

@lock lock bot locked as resolved and limited conversation to collaborators Jul 12, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants