Merge pull request #1308 from matrix-org/j94/release-process

Document release process in CONTRIBUTING.md

Author: Christian Paul

CONTRIBUTING.md

@@ -57,3 +57,21 @@ new code.
    directly onto the `package.json` (NPM) version.
  - Releases are also tagged so they are present on the Releases page on Github.
  - Releases should be signed by the maintainer's key.
+
+### Doing a release
+
+These steps are for the maintainers of the IRC bridge to refer to when doing a release.
+When doing an RC release, suffix a `-rcV` to the tag and version but NOT the branch.
+
+* `git checkout develop`
+* `git pull`
+* `git switch -c release-v0.V.0`
+* update package.json version number
+* `npm install` to update package-lock.json
+* `./scripts/changelog-release.sh`
+* `git commit CHANGELOG.md changelog.d package.json package-lock.json -m 'v0.V.0'`
+* `git tag --sign --message 'v0.V.0' '0.V.0'`
+* `git push origin release-v0.V.0`
+* `git push origin 0.V.0`
+* [Make a release on GitHub](https://github.com/matrix-org/matrix-appservice-irc/releases), copying the changelog into the body and marking it as pre-release
+* `npm publish`

changelog.d/1308.doc

@@ -0,0 +1 @@
+Document release process in CONTRIBUTING.md

spec/util/test.js

@@ -25,7 +25,7 @@ const main = proxyquire("../../lib/main.js", {
 jasmine.getEnv().addReporter({
     specStarted: function(result) {
         console.log(result.fullName);
-        console.log(new Array(2 + result.fullName.length).join("="));
+        console.log("=".repeat(result.fullName.length + 1));
     }
 });