Skip to content
This repository has been archived by the owner on Sep 1, 2023. It is now read-only.

Commit

Permalink
Merge pull request #1211 from vitaly-krugl/minor-cleanup-in-release-md
Browse files Browse the repository at this point in the history
Minor corrections in RELEASE.md
  • Loading branch information
vitaly-krugl committed Jan 19, 2017
2 parents 3c1480d + 2ad4e19 commit ba84637
Showing 1 changed file with 6 additions and 6 deletions.
12 changes: 6 additions & 6 deletions RELEASE.md
Original file line number Diff line number Diff line change
@@ -1,24 +1,24 @@
# Release Process

1. Send announcement that a release is underway to the committer's lounge on
1. Send an announcement that a release is underway to the committer's lounge on
discourse.numenta.org and ask reviewers not to merge PRs in nupic.core until
you're done with the release.
2. Create a PR that includes:
- Release notes added to CHANGELOG.md
- Change to the VERSION file so it matches the intended release version
3. Wait for the PR to be approved and merged, and the Bamboo build to complete
successfully, along with the AppVeyor and Travis builds.
4. Fetch the additional artifiacts (from AppVeyor and Travis) in Bamboo via the
successfully, along with the corresponding AppVeyor and Travis builds.
4. Fetch the additional nupic.core artifacts (from AppVeyor and Travis) in Bamboo via the
run button at top, selecting "Run stage 'Stage Release'".
5. Create a "release" in Bamboo with a version matching the intended release
version
6. Deploy the release in Bamboo. This will:
- Validate that the Bamboo release number matches the wheel version
- Push the wheel to PyPI
- Validate that the Bamboo release number matches the wheel versions.
- Push the wheels to PyPI
7. Create a new Github "Release" at https://github.com/numenta/nupic.core/releases/new
- Along with the creation of the release, there is an option to create a git tag with the release. Name it "X.Y.Z" and point it to the commit SHA for the merged PR described in #2 above.
- Release title should be "X.Y.Z"
- Release description should be the latest changelog
8. Create a PR that includes the following, and wait for this PR to be approved and merged:
- Change to the VERSION file with the next expected release and ".dev0" as suffix. For example, if the release was 0.5.0, then change it to 0.5.1.dev0
9. Send announcement to the committer's lounge on discourse.numenta.org that the release is complete.
9. Send an announcement to the committer's lounge on discourse.numenta.org that the release is complete.

0 comments on commit ba84637

Please sign in to comment.