short tl;dr; of the release
- Robustness and quality
- Ensure that all tests are passing, this includes:
- unit
- Publish a release candidate to npm
# Minor prerelease (e.g. 0.24.1 -> 0.25.0-rc.0) $ npx aegir release --type preminor -t node -t browser --preid rc --dist-tag next # Increment prerelease (e.g. 0.25.0-rc.0 -> 0.25.0-rc.1) $ npx aegir release --type prerelease -t node -t browser --preid rc --dist-tag next
- Run tests of the following projects with the new release:
- Ensure that all tests are passing, this includes:
- Documentation
- Ensure that README.md is up to date
- Ensure that all the examples run
- Communication
- Create the release issue
- Take a snapshot between of everyone that has contributed to this release (including its subdeps in IPFS, libp2p, IPLD and multiformats) using
name-your-contributors. Generate a nice markdown list with this script - Announcements (both pre-release and post-release)
- IRC
- discuss.ipfs.io
- Blog post
- Copy release notes to the GitHub Release description
In alphabetical order, here are all the humans that contributed to the release:
- ...
Would you like to contribute to the libp2p project and don't know how? Well, there are a few places you can get started:
- Check the issues with the
help wantedlabel at the Ready column in our waffle board - https://waffle.io/libp2p/js-libp2p?label=help%20wanted - Join an IPFS All Hands, introduce yourself and let us know where you would like to contribute - https://github.com/ipfs/team-mgmt#all-hands-call
- 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 ⚡️ⒿⓈ Core Dev Team Weekly Sync 🙌🏽 and be part of the Sprint action!
The best place to ask your questions about libp2p, how it works and what you can do with it is at discuss.ipfs.io. We are also available at the #libp2p channel on Freenode.