bigchaindb/js-bigchaindb-driver
1
0
Fork 0
mirror of https://github.com/bigchaindb/js-bigchaindb-driver.git synced 2024-11-22 01:36:56 +01:00
Code Releases Activity
84bd4efe03
js-bigchaindb-driver/RELEASE_PROCESS.md
getlarge 1b9bafa097
fix: regenerate doc 
Signed-off-by: getlarge <ed@getlarge.eu>
2021-03-10 08:48:56 +01:00

4.6 KiB
Raw Blame History

Our Release Process

Notes

BigchainDB follows the Python form of Semantic Versioning (i.e. MAJOR.MINOR.PATCH), which is almost identical to regular semantic versioning, but there's no hyphen, e.g.

  • 0.9.0 for a typical final release
  • 4.5.2a1 not 4.5.2-a1 for the first Alpha release
  • 3.4.5rc2 not 3.4.5-rc2 for Release Candidate 2

Note: For Git tags (which are used to identify releases on GitHub), we append a v in front.

We follow BEP-1, which is our variant of C4, the Collective Code Construction Contract, so a release is just a tagged commit on the master branch, i.e. a label for a particular Git commit.

Steps

  1. Make sure you have a recent version of node and npm.

  2. npm install

  3. Update all npm package dependencies, where possible. You might have to freeze some versions. Run all tests locally (npm run test) and make sure they pass. Make a pull request (to be merged into the master branch) and make sure all tests are passing there (in Travis). Merge the pull request.

  4. Make sure your local master branch is in sync with GitHub: git checkout master and git pull

  5. Do a test build:

    npm run build

    If that fails, then get it working.

  6. We use the release-it package (from npm) to automate most of the release. Make sure you have a recent version.

  7. Login to npm using your npm credentials, so you can publish a new bigchaindb-driver package there. (The npm account must have permission to do so).

    npm login

  8. release-it needs a Github personal access token so it can interact with GitHub on your behalf. To get one, go to:

    https://github.com/settings/tokens

    and then make that token available as an environment variable, e.g.

    export GITHUB_TOKEN="f941e0..."

  9. Do the release:

    • For a patch release, do npm run release
    • For a minor release, do npm run release-minor
    • For a major release, do npm run release-major

    If your npm account is using two-factor authentication, you will have to append a one-time password (OTP) like --npm.otp=123456. The above command will automatically do a bunch of things:

    • bump the project version in package.json, then git commit and git push it.
    • create a new Git tag of the form v{verson}, e.g. v1.2.3
    • create a new GitHub release.
    • publish a new npm release

    To see all the arguments passed to release-it, search for "release" in package.json. The arguments are documented in the release-it GitHub repo.

  10. Make sure everything worked as expected.

  11. You can edit the description of the GitHub release to add or remove details.

If the docs were updated since the last release, login to readthedocs.org and go to the BigchainDB JavaScript Driver project, then:

  1. Click on "Builds", select "latest" from the drop-down menu, then click the "Build Version:" button.

  2. Wait for the build of "latest" to finish. This can take a few minutes.

  3. Go to Admin --> Advanced Settings and make sure that "Default branch:" (i.e. what "latest" points to) is set to the new release's tag, e.g. v0.9.1. (It won't be an option if you didn't wait for the build of "latest" to finish.) Then scroll to the bottom and click "Save".

  4. Go to Admin --> Versions and under Choose Active Versions, do these things:

    1. Make sure that the new version's tag is "Active" and "Public"
    2. Make sure the stable branch is not active.
    3. Scroll to the bottom of the page and click "Save".

Congratulations, you have released a new version of the BigchainDB JavaScript Driver!