From 9bb15f232f14220c587f33d71e7a6a159d4149ba Mon Sep 17 00:00:00 2001 From: Steven Allen Date: Thu, 11 Jul 2019 00:21:48 -0700 Subject: [PATCH 1/4] releases: switch to a soft release model And other nits. --- docs/RELEASE_TEMPLATE.md | 27 ++++++ docs/releases.md | 187 +++++++++++++++++++-------------------- 2 files changed, 117 insertions(+), 97 deletions(-) create mode 100644 docs/RELEASE_TEMPLATE.md diff --git a/docs/RELEASE_TEMPLATE.md b/docs/RELEASE_TEMPLATE.md new file mode 100644 index 00000000000..ec50089694f --- /dev/null +++ b/docs/RELEASE_TEMPLATE.md @@ -0,0 +1,27 @@ +# Go-IPFS Changelog Template + +## X.Y.Z YYYY-MM-DD + +We're happy to announce go-ipfs X.Y.Z, bla bla... + +< release notes > + +### Contributors + +< list generated by bin/mkreleaselog > + +Would you like to contribute to the IPFS project and don't know how? Well, there are a few places you can get started: + +- Check the issues with the `help wanted` label in the [go-ipfs repo](https://github.com/ipfs/go-ipfs/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22) +- Join an IPFS All Hands, introduce yourself and let us know where you would like to contribute - https://github.com/ipfs/team-mgmt/#weekly-ipfs-all-hands +- Hack with IPFS and show us what you made! The All Hands call is also the perfect venue for demos, join in and show us what you built +- Join the discussion at http://discuss.ipfs.io/ and help users finding their answers. +- Join the [Go Core Dev Team Weekly Sync](https://github.com/ipfs/team-mgmt/issues/650) and be part of the Sprint action! + +### ⁉️ Do you have questions? + +The best place to ask your questions about IPFS, how it works and what you can do with it is at [discuss.ipfs.io](http://discuss.ipfs.io). We are also available at the `#ipfs` channel on Freenode, which is also [accessible through our Matrix bridge](https://riot.im/app/#/room/#freenode_#ipfs:matrix.org). + +### Changelog + +< changelog generated by bin/mkreleaselog > diff --git a/docs/releases.md b/docs/releases.md index 56b412f9a56..9284db2bf98 100644 --- a/docs/releases.md +++ b/docs/releases.md @@ -9,7 +9,7 @@ ## Release Philosophy -`go-ipfs` aims to have release every six weeks, two releases per quarter. During these 6 week releases, we go through 4 different stages of Release Candidates (RC) that gives us the opportunity to test the new version against our test environments (unit, interop, integration), QA in our current production environment, IPFS apps (e.g. Desktop and WebUI) and with our _early testers_[1] that have IPFS running in Production, by leveraging their own test infrastructure and QA systems. +`go-ipfs` aims to have release every six weeks, two releases per quarter. During these 6 week releases, we go through 4 different stages that gives us the opportunity to test the new version against our test environments (unit, interop, integration), QA in our current production environment, IPFS apps (e.g. Desktop and WebUI) and with our community and _early testers_[1] that have IPFS running in Production. We might expand the six week release schedule in case of: - No new updates to be added @@ -17,20 +17,41 @@ We might expand the six week release schedule in case of: ## Release Flow -`go-ipfs` releases come in 4 stages: +`go-ipfs` releases come in 4 stages designed to gradually roll out changes and reduce the impact of any regressions that may have been introduced. If we need to merge non-trivial features/fixes during the process, we start over at stage 1. -- **Release Stage 1 - Internal testing** - Test the Release against our testing infrastructure, including interoperability, integration, test lab, multiple runtimes and the apps we've built (WebUI, Desktop, NPM on IPFS, HTTP Client Libraries). The intent is to make this stage fully automated (and somewhat is already), until then, we manually check a list and ensure that all tests have been run -- **Release Stage 2 - Invite _early testers_ to try it out** - Reach out to our _early testers_ (i.e. projects that have volunteered to support `go-ipfs` by using their own test infrastructure and tell us the results) -- **Release Stage 3 - Announce to the broader community** - Communicate to the community that a new Release Candidate is ready and that everyone is welcome to test it with us -- **Release Stage 4 - Complete the Release** - Finalize the release, start the next release. +### Stage 1 - Internal Testing -The Release Stages are not linked to Release Candidate numbers, in fact, there can be multiple release candidate per stages as we catch bugs and improve the release itself. +Before this stage, we expect _all_ tests (interop, testlab, performance, etc.) to pass. -

- - - -

+At this stage, we'll: + +1. Start a partial-rollout to our own infrastructure. +2. Test against ipfs and ipfs-shipyard applications. + +**Goal(s):** + +1. Make sure we haven't introduced any obvious regressions. +2. Test the release in an environment we can monitor and easily roll back (i.e., our own infra). + +### Stage 2 - Public Beta + +At this stage, we'll announce the impending release to the community and ask for beta testers. + +**Goal:** Test the release in as many non-production environments as possible. This is relatively low-risk but gives us a _breadth_ of testing internal testing can't. + +### Stage 3 - Soft Release + +At this stage, we consider the release to be "production ready" and ask will ask the community and our early testers to (partially) deploy the release to their production infrastructure. + +**Goal(s):** + +1. Test the release in some production environments with heavy workloads. +2. Partially roll-out an upgrade to see how it affects the network. +3. Retain the ability to ship last-minute fixes before the final release. + +### Stage 4 - Release + +At this stage, the release is "battle hardened" and ready for wide deployment. ## Performing a Release @@ -54,91 +75,63 @@ The first step is for the `Lead Maintainer` for `go-ipfs` to open an issue with # ✅ Release Checklist For each RC published in each stage: -- [ ] version string in `version.go` has been updated -- [ ] tag commit with vX.Y.Z-rcN - -### Release Stage 1 - Internal testing - -When Release Stage 1, there is a features freeze for the release branch. - -- [ ] CHANGELOG.md has been updated - - use `./bin/mkreleaselog` to generate a nice starter list -- [ ] Automated Testing - Ensure that all tests are passing, this includes: - - [ ] unit - - [ ] sharness - - [ ] [interop](https://github.com/ipfs/interop#test-with-a-non-yet-released-version-of-go-ipfs) -- [ ] Network Testing: - - [ ] test lab things -- [ ] Infrastructure Testing: - - [ ] Deploy new version to a subset of Bootstrappers - - [ ] Deploy new version to a subset of Gateways - - [ ] Deploy new version to a subset of Preload nodes - - [ ] Collect metrics every day. Work with the Infrastructure team to learn of any hiccup -- [ ] IPFS HTTP Client Libraries Testing: - - [ ] [JS](http://github.com/ipfs/js-ipfs-http-client) - - [ ] [Go](https://github.com/ipfs/go-ipfs-api) -- [ ] IPFS Application Testing - Run the tests of the following applications: - - [ ] WebUI - - [ ] IPFS Desktop - - [ ] IPFS Companion - - [ ] NPM on IPFS - -### Release Stage 2 - Invite _early testers_ to try it out - -- [ ] Reach out to the IPFS _early testers_ listed below for testing this release (check when no more problems have been reported). - - [ ] **COPY THE LIST FROM `docs/EARLY_TESTERS.md`** -- [ ] Run tests available in the following repos with the latest RC (check when all tests pass): - - [ ] [orbit-db](https://github.com/orbitdb/orbit-db) - -PSA: If you are a heavy user of `go-ipfs`, have developed a solid test infrastructure for your application and would love to help us would like to help us test `go-ipfs` release candidates, reach out to go-ipfs-wg@ipfs.io. - -### Release Stage 3 - Announce to the broader community - -- [ ] Documentation - - [ ] Ensure that CHANGELOG.md is up to date - - [ ] Ensure that README.md is up to date - - [ ] Ensure that all the examples we have produced for go-ipfs run without problems - - [ ] Update HTTP-API Documentation on the Website using https://github.com/ipfs/http-api-docs -- [ ] Invite the community through (link to the release issue): - - [ ] [discuss.ipfs.io](https://discuss.ipfs.io/c/announcements) - - [ ] Twitter - - [ ] IRC - -### Release Stage 4 - Complete the Release - -- [ ] Final preparation - - [ ] Verify that version string in `repo/version.go` has been updated - - [ ] tag commit with vX.Y.Z - - [ ] update release branch to point to release commit (`git merge vX.Y.Z`). - - [ ] publish dist.ipfs.io - - [ ] publish next version to https://github.com/ipfs/npm-go-ipfs -- [ ] Publish a Release Blog post (at minimum, a c&p of this release issue with all the highlights, API changes, link to changelog and thank yous) -- [ ] Broadcasting (link to blog post) - - [ ] Twitter - - [ ] IRC - - [ ] Reddit - - [ ] [discuss.ipfs.io](https://discuss.ipfs.io/c/announcements) - - [ ] Announce it on the [IPFS Users mlist](https://groups.google.com/forum/#!forum/ipfs-users) - -# ❤️ Huge thank you to everyone that made this release possible - -In alphabetical order, here are all the humans that contributed to the release: - -- - -# 🙌🏽 Want to contribute? - -Would you like to contribute to the IPFS project and don't know how? Well, there are a few places you can get started: - -- Check the issues with the `help wanted` label in the [go-ipfs repo](https://github.com/ipfs/go-ipfs/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22) -- Join an IPFS All Hands, introduce yourself and let us know where you would like to contribute - https://github.com/ipfs/team-mgmt/#weekly-ipfs-all-hands -- Hack with IPFS and show us what you made! The All Hands call is also the perfect venue for demos, join in and show us what you built -- Join the discussion at http://discuss.ipfs.io/ and help users finding their answers. -- Join the [Go Core Dev Team Weekly Sync](https://github.com/ipfs/team-mgmt/issues/650) and be part of the Sprint action! - -# ⁉️ Do you have questions? - -The best place to ask your questions about IPFS, how it works and what you can do with it is at [discuss.ipfs.io](http://discuss.ipfs.io). We are also available at the `#ipfs` channel on Freenode, which is also [accessible through our Matrix bridge](https://riot.im/app/#/room/#freenode_#ipfs:matrix.org). + +- version string in `version.go` has been updated +- tag commit with vX.Y.Z-rcN + +- [ ] Stage 1 - Internal Testing + - [ ] Feature freeze. If any non-trivial features get added to the release, uncheck all the checkboxes and return to this stage. + - [ ] CHANGELOG.md has been updated + - use `./bin/mkreleaselog` to generate a nice starter list + - use `./doc/RELEASE_TEMPLATE.md` as a template + - [ ] Automated Testing (already tested in CI) - Ensure that all tests are passing, this includes: + - [ ] unit + - [ ] sharness + - [ ] [interop](https://github.com/ipfs/interop#test-with-a-non-yet-released-version-of-go-ipfs) + - [ ] go-ipfs-api + - [ ] go-ipfs-http-client + - [ ] Network Testing: + - [ ] test lab things + - [ ] Infrastructure Testing: + - [ ] Deploy new version to a subset of Bootstrappers + - [ ] Deploy new version to a subset of Gateways + - [ ] Deploy new version to a subset of Preload nodes + - [ ] Collect metrics every day. Work with the Infrastructure team to learn of any hiccup + - [ ] IPFS Application Testing - Run the tests of the following applications: + - [ ] WebUI + - [ ] IPFS Desktop + - [ ] IPFS Companion + - [ ] NPM on IPFS +- [ ] Stage 2 - Public Beta + - [ ] Reach out to the IPFS _early testers_ listed in `docs/EARLY_TESTERS.md` for testing this release (check when no more problems have been reported). If you'd like to be added to this list, please file a PR. + - [ ] Reach out to on IRC for beta testers. + - [ ] Run tests available in the following repos with the latest beta (check when all tests pass): + - [ ] [orbit-db](https://github.com/orbitdb/orbit-db) +- [ ] Stage 3 - Soft Release + - [ ] Documentation + - [ ] Ensure that CHANGELOG.md is up to date + - [ ] Ensure that README.md is up to date + - [ ] Ensure that all the examples we have produced for go-ipfs run without problems + - [ ] Update HTTP-API Documentation on the Website using https://github.com/ipfs/http-api-docs + - [ ] Invite the IPFS _early testers_ to deploy the release to part of their production infrastructure. + - [ ] Invite the wider community through (link to the release issue): + - [ ] [discuss.ipfs.io](https://discuss.ipfs.io/c/announcements) + - [ ] Twitter + - [ ] IRC +- [ ] Stage 4 - Release + - [ ] Final preparation + - [ ] Verify that version string in `repo/version.go` has been updated + - [ ] tag commit with vX.Y.Z + - [ ] update release branch to point to release commit (`git merge vX.Y.Z`). + - [ ] publish dist.ipfs.io + - [ ] publish next version to https://github.com/ipfs/npm-go-ipfs + - [ ] Publish a Release Blog post (at minimum, a c&p of this release issue with all the highlights, API changes, link to changelog and thank yous) + - [ ] Broadcasting (link to blog post) + - [ ] Twitter + - [ ] IRC + - [ ] Reddit + - [ ] [discuss.ipfs.io](https://discuss.ipfs.io/c/announcements) + - [ ] Announce it on the [IPFS Users mlist](https://groups.google.com/forum/#!forum/ipfs-users) ``` ## Release Version Numbers (aka semver) From 72b9c4a355cfb63abf0c28eca6810495d16f4999 Mon Sep 17 00:00:00 2001 From: David Dias Date: Fri, 12 Jul 2019 16:22:02 +0100 Subject: [PATCH 2/4] Update and rename RELEASE_TEMPLATE.md to RELEASE_ISSUE_TEMPLATE.md --- ..._TEMPLATE.md => RELEASE_ISSUE_TEMPLATE.md} | 19 +++++++++++-------- 1 file changed, 11 insertions(+), 8 deletions(-) rename docs/{RELEASE_TEMPLATE.md => RELEASE_ISSUE_TEMPLATE.md} (87%) diff --git a/docs/RELEASE_TEMPLATE.md b/docs/RELEASE_ISSUE_TEMPLATE.md similarity index 87% rename from docs/RELEASE_TEMPLATE.md rename to docs/RELEASE_ISSUE_TEMPLATE.md index ec50089694f..87cf26d1f29 100644 --- a/docs/RELEASE_TEMPLATE.md +++ b/docs/RELEASE_ISSUE_TEMPLATE.md @@ -1,12 +1,18 @@ -# Go-IPFS Changelog Template +> Release Issue Template -## X.Y.Z YYYY-MM-DD +# go-ipfs X.Y.Z Release We're happy to announce go-ipfs X.Y.Z, bla bla... -< release notes > +## Highlights -### Contributors +< top highlights for this release notes > + +## Changelog + +< changelog generated by bin/mkreleaselog > + +## Contributors < list generated by bin/mkreleaselog > @@ -18,10 +24,7 @@ Would you like to contribute to the IPFS project and don't know how? Well, there - Join the discussion at http://discuss.ipfs.io/ and help users finding their answers. - Join the [Go Core Dev Team Weekly Sync](https://github.com/ipfs/team-mgmt/issues/650) and be part of the Sprint action! -### ⁉️ Do you have questions? +## ⁉️ Do you have questions? The best place to ask your questions about IPFS, how it works and what you can do with it is at [discuss.ipfs.io](http://discuss.ipfs.io). We are also available at the `#ipfs` channel on Freenode, which is also [accessible through our Matrix bridge](https://riot.im/app/#/room/#freenode_#ipfs:matrix.org). -### Changelog - -< changelog generated by bin/mkreleaselog > From a32d5e973440c957e535ebb072842e53a9108228 Mon Sep 17 00:00:00 2001 From: David Dias Date: Fri, 12 Jul 2019 16:25:56 +0100 Subject: [PATCH 3/4] Update releases.md --- docs/releases.md | 89 +++--------------------------------------------- 1 file changed, 5 insertions(+), 84 deletions(-) diff --git a/docs/releases.md b/docs/releases.md index 9284db2bf98..ff1eb7bd668 100644 --- a/docs/releases.md +++ b/docs/releases.md @@ -24,14 +24,12 @@ We might expand the six week release schedule in case of: Before this stage, we expect _all_ tests (interop, testlab, performance, etc.) to pass. At this stage, we'll: - -1. Start a partial-rollout to our own infrastructure. -2. Test against ipfs and ipfs-shipyard applications. +- 1. Start a partial-rollout to our own infrastructure. +- 2. Test against ipfs and ipfs-shipyard applications. **Goal(s):** - -1. Make sure we haven't introduced any obvious regressions. -2. Test the release in an environment we can monitor and easily roll back (i.e., our own infra). +- 1. Make sure we haven't introduced any obvious regressions. +- 2. Test the release in an environment we can monitor and easily roll back (i.e., our own infra). ### Stage 2 - Public Beta @@ -55,84 +53,7 @@ At this stage, the release is "battle hardened" and ready for wide deployment. ## Performing a Release -The first step is for the `Lead Maintainer` for `go-ipfs` to open an issue with Title `go-ipfs Release` and a c&p of the following template: - -``` -> - -# 🗺 What's left for release - - - -# 🔦 Highlights - - - -# 🏗 API Changes - - - -# ✅ Release Checklist - -For each RC published in each stage: - -- version string in `version.go` has been updated -- tag commit with vX.Y.Z-rcN - -- [ ] Stage 1 - Internal Testing - - [ ] Feature freeze. If any non-trivial features get added to the release, uncheck all the checkboxes and return to this stage. - - [ ] CHANGELOG.md has been updated - - use `./bin/mkreleaselog` to generate a nice starter list - - use `./doc/RELEASE_TEMPLATE.md` as a template - - [ ] Automated Testing (already tested in CI) - Ensure that all tests are passing, this includes: - - [ ] unit - - [ ] sharness - - [ ] [interop](https://github.com/ipfs/interop#test-with-a-non-yet-released-version-of-go-ipfs) - - [ ] go-ipfs-api - - [ ] go-ipfs-http-client - - [ ] Network Testing: - - [ ] test lab things - - [ ] Infrastructure Testing: - - [ ] Deploy new version to a subset of Bootstrappers - - [ ] Deploy new version to a subset of Gateways - - [ ] Deploy new version to a subset of Preload nodes - - [ ] Collect metrics every day. Work with the Infrastructure team to learn of any hiccup - - [ ] IPFS Application Testing - Run the tests of the following applications: - - [ ] WebUI - - [ ] IPFS Desktop - - [ ] IPFS Companion - - [ ] NPM on IPFS -- [ ] Stage 2 - Public Beta - - [ ] Reach out to the IPFS _early testers_ listed in `docs/EARLY_TESTERS.md` for testing this release (check when no more problems have been reported). If you'd like to be added to this list, please file a PR. - - [ ] Reach out to on IRC for beta testers. - - [ ] Run tests available in the following repos with the latest beta (check when all tests pass): - - [ ] [orbit-db](https://github.com/orbitdb/orbit-db) -- [ ] Stage 3 - Soft Release - - [ ] Documentation - - [ ] Ensure that CHANGELOG.md is up to date - - [ ] Ensure that README.md is up to date - - [ ] Ensure that all the examples we have produced for go-ipfs run without problems - - [ ] Update HTTP-API Documentation on the Website using https://github.com/ipfs/http-api-docs - - [ ] Invite the IPFS _early testers_ to deploy the release to part of their production infrastructure. - - [ ] Invite the wider community through (link to the release issue): - - [ ] [discuss.ipfs.io](https://discuss.ipfs.io/c/announcements) - - [ ] Twitter - - [ ] IRC -- [ ] Stage 4 - Release - - [ ] Final preparation - - [ ] Verify that version string in `repo/version.go` has been updated - - [ ] tag commit with vX.Y.Z - - [ ] update release branch to point to release commit (`git merge vX.Y.Z`). - - [ ] publish dist.ipfs.io - - [ ] publish next version to https://github.com/ipfs/npm-go-ipfs - - [ ] Publish a Release Blog post (at minimum, a c&p of this release issue with all the highlights, API changes, link to changelog and thank yous) - - [ ] Broadcasting (link to blog post) - - [ ] Twitter - - [ ] IRC - - [ ] Reddit - - [ ] [discuss.ipfs.io](https://discuss.ipfs.io/c/announcements) - - [ ] Announce it on the [IPFS Users mlist](https://groups.google.com/forum/#!forum/ipfs-users) -``` +The first step is for the `Lead Maintainer` for `go-ipfs` to open an issue with Title `go-ipfs Release` and a c&p of the [RELEASE_ISSUE_TEMPLATE](./RELEASE_ISSUE_TEMPLATE.md) ## Release Version Numbers (aka semver) From 63f6699037b86d66adc06e6c6f4fa0d9e8399999 Mon Sep 17 00:00:00 2001 From: David Dias Date: Fri, 12 Jul 2019 16:26:09 +0100 Subject: [PATCH 4/4] Update RELEASE_ISSUE_TEMPLATE.md --- docs/RELEASE_ISSUE_TEMPLATE.md | 68 +++++++++++++++++++++++++++++++++- 1 file changed, 66 insertions(+), 2 deletions(-) diff --git a/docs/RELEASE_ISSUE_TEMPLATE.md b/docs/RELEASE_ISSUE_TEMPLATE.md index 87cf26d1f29..286ed06cc68 100644 --- a/docs/RELEASE_ISSUE_TEMPLATE.md +++ b/docs/RELEASE_ISSUE_TEMPLATE.md @@ -4,7 +4,11 @@ We're happy to announce go-ipfs X.Y.Z, bla bla... -## Highlights +## 🗺 What's left for release + + + +## 🔦 Highlights < top highlights for this release notes > @@ -12,7 +16,67 @@ We're happy to announce go-ipfs X.Y.Z, bla bla... < changelog generated by bin/mkreleaselog > -## Contributors +## ✅ Release Checklist + +For each RC published in each stage: + +- version string in `version.go` has been updated +- tag commit with vX.Y.Z-rcN +- [ ] Stage 1 - Internal Testing + - [ ] Feature freeze. If any non-trivial features get added to the release, uncheck all the checkboxes and return to this stage. + - [ ] CHANGELOG.md has been updated + - use `./bin/mkreleaselog` to generate a nice starter list + - use `./doc/RELEASE_TEMPLATE.md` as a template + - [ ] Automated Testing (already tested in CI) - Ensure that all tests are passing, this includes: + - [ ] unit + - [ ] sharness + - [ ] [interop](https://github.com/ipfs/interop#test-with-a-non-yet-released-version-of-go-ipfs) + - [ ] go-ipfs-api + - [ ] go-ipfs-http-client + - [ ] Network Testing: + - [ ] test lab things + - [ ] Infrastructure Testing: + - [ ] Deploy new version to a subset of Bootstrappers + - [ ] Deploy new version to a subset of Gateways + - [ ] Deploy new version to a subset of Preload nodes + - [ ] Collect metrics every day. Work with the Infrastructure team to learn of any hiccup + - [ ] IPFS Application Testing - Run the tests of the following applications: + - [ ] WebUI + - [ ] IPFS Desktop + - [ ] IPFS Companion + - [ ] NPM on IPFS +- [ ] Stage 2 - Public Beta + - [ ] Reach out to the IPFS _early testers_ listed in `docs/EARLY_TESTERS.md` for testing this release (check when no more problems have been reported). If you'd like to be added to this list, please file a PR. + - [ ] Reach out to on IRC for beta testers. + - [ ] Run tests available in the following repos with the latest beta (check when all tests pass): + - [ ] [orbit-db](https://github.com/orbitdb/orbit-db) +- [ ] Stage 3 - Soft Release + - [ ] Documentation + - [ ] Ensure that CHANGELOG.md is up to date + - [ ] Ensure that README.md is up to date + - [ ] Ensure that all the examples we have produced for go-ipfs run without problems + - [ ] Update HTTP-API Documentation on the Website using https://github.com/ipfs/http-api-docs + - [ ] Invite the IPFS _early testers_ to deploy the release to part of their production infrastructure. + - [ ] Invite the wider community through (link to the release issue): + - [ ] [discuss.ipfs.io](https://discuss.ipfs.io/c/announcements) + - [ ] Twitter + - [ ] IRC +- [ ] Stage 4 - Release + - [ ] Final preparation + - [ ] Verify that version string in `repo/version.go` has been updated + - [ ] tag commit with vX.Y.Z + - [ ] update release branch to point to release commit (`git merge vX.Y.Z`). + - [ ] publish dist.ipfs.io + - [ ] publish next version to https://github.com/ipfs/npm-go-ipfs + - [ ] Publish a Release Blog post (at minimum, a c&p of this release issue with all the highlights, API changes, link to changelog and thank yous) + - [ ] Broadcasting (link to blog post) + - [ ] Twitter + - [ ] IRC + - [ ] Reddit + - [ ] [discuss.ipfs.io](https://discuss.ipfs.io/c/announcements) + - [ ] Announce it on the [IPFS Users mlist](https://groups.google.com/forum/#!forum/ipfs-users) + +## ❤️ Contributors < list generated by bin/mkreleaselog >