-
Notifications
You must be signed in to change notification settings - Fork 3
Release Process
Starting with tupelo v0.1.0, we will make a release plan for each release that increments the middle (minor) version number. The major version number will remain at 0 for now, and the patch number will be used for bug fix releases that don't add any new features. These bug fix releases don't need their own plans, but feel free to make one if you feel it would benefit the release.
Each release's plan should be created as a both a new wiki page and a milestone on the tupelo GitHub project. They should link to each other.
Each release plan should include the following:
- The cards that are blockers for that release (i.e. they must go in).
- Any cards that are nice-to-haves but not essential in that release.
- Any cards that should not go into that release, for whatever reason.
- The 1-2 additional release process, infrastructure, etc. improvement(s) we are going to do for that release.
See the Plans section below. Add your new release plan link to the top of that list.
Be disciplined about following the plan. It's OK to change the plan with consensus from the team, and then follow the new plan. But we should not ignore nor arbitrarily deviate from the plan.
As items are completed (e.g. merged to master), cross them off in the release plan by putting double-tildes around them like this.