- Review the state of the current milestone
- Go through telemetry for GDPR
- Go through all merged pull requests and add the
validate fixlabel as appropriate as well as checking for news entries - Validate fixed issues
- Triage unverified issues
- Update pre-existing dependencies as appropriate (npm, Python, git submodule, or otherwise; requires updating CELA)
- Evaluate if TypeScript usage needs updating to sync with VS Code's usage
- Evaluate projects &
metaissues - Go through
needs PRissues to see if there's anything we want to add to this milestone - Finalize the initial set of issues for the milestone
- Close issues that have needed more info for over a month
- Review the state of the current milestone
- Go through telemetry for GDPR
- Go through all merged pull requests and add the
validate fixlabel as appropriate as well as checking for news entries - Validate fixed issues
- Triage unverified issues
- Check if there have been no performance regressions
- Read through VS Code's iteration plan (it may still be a draft)
- Review the state of the current milestone
- Go through telemetry for GDPR
- Go through all merged pull requests and add the
validate fixlabel as appropriate as well as checking for news entries - Validate fixed issues
- Triage unverified issues
- Announce the lock-down of dependencies for this release
- Notify CELA of all changes to the repository, distribution dependencies (including ptvsd as necessary)
- Update the version to be a
beta& update the changelog - Announce the beta development build (along with how to help validate fixes)
- Open appropriate documentation issues
- Review the state of the current milestone
- Go through telemetry for GDPR
- Merge any last-minute pull requests
- Go through all merged pull requests and add the
validate fixlabel as appropriate as well as checking for news entries - Validate fixed issues
- Triage unverified issues
- Announce feature freeze
- Make sure the repo and distribution TPNs have been updated appropriately
- Update the version to be an
rc& update the changelog - Announce the release candidate development build
- Open appropriate documentation issues
- Begin drafting a blog post
- Ensure all new feature usages are tracked via telemetry
- Make sure no extraneous files are being included in the
.vsixfile (make sure to check for hidden files) - Make sure the appropriate pull requests for the documentation -- including the WOW page -- are ready
- Update the changelog (including the names of external contributors & projects)
- Update the version number to be final
- Make sure CI is passing
- Generate the final
.vsixfile - Upload the final
.vsixfile to the marketplace - Publish documentation changes
- Publish the blog post
- Create a release on GitHub (which creates an appropriate git tag)
- Determine if a hotfix is needed
- Create the
release-branch
- 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 any straggling fixed issues needing validation
- Close the (now) old milestone
- Delete the previous releases' branch
- Go through
needs more infoissues and close any that have no activity for over a month