Skip to content

Release plan for January 2018 #547

Closed
@brettcannon

Description

@brettcannon

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)

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions