The early testers programme allows groups using js-ipfs in production to self-volunteer to help test js-ipfs release candidates to ensure that no regressions that might affect production systems make it into the final release. While we invite the entire community to help test releases, members of the early testers program are expected to participate directly and actively in every release.
Members of the early tester program are expected to work closely with us to:
- Provide high quality, actionable feedback.
- Work directly with us to debug regressions in the release.
- Help ensure a rock-solid, timely release.
We will ask early testers to participate at two points in the process:
- When js-ipfs enters the second release stage, early testers will be asked to test js-ipfs on non-production infrastructure. This may involve things like:
- Running integration tests against the release candidate.
- Running simulations/benchmarks on the release candidate.
- Manually testing the release candidate to check for regressions.
- When js-ipfs enters the third release stage (soft release), early testers will be asked to partially deploy the release candidate to production infrastructure. Release candidates at this stage are expected to be identical to the final release. However, this stage allows the js-ipfs team to fix any last-minute regressions without cutting an entirely new release.
- npm-on-ipfs - install your dependencies via the distributed web!
- orbit-db - Peer-to-Peer Databases for the Decentralized Web
- ipfs-log - Append-only log CRDT on IPFS
- Sidetree DID Protocol - Decentralized Identifier Layer-2 network protocol
- Constellation - Distributed scientific databases for citizen science and more
Simply submit a PR to this document by adding your project name and contact.