- Implement fixes, features, changes, and create a release candidate version in the format x.x.x-rc.x
- Compile a version of the ziptest application in the standalone kangaroo app runtime using this release candidate version
- Perform smoke test over 2 consecutive days:
- Group of 3 testers
- All nodes go online.
- Each node sends 10 signals to each peer individually.
- Each node sends 10 signals to "Everyone".
- Each node creates 10 entries, 1 rep.
- Wait for entries to appear for all participants.
- One node goes offline.
- Remaining nodes create another 10 entries, 1 rep.
- Wait for entries to appear again.
- Offline node stays offline for 15 minutes, then goes online and waits for entries to appear. 15 minutes is the cutoff point for "what's new" to ring/disc sync
- Create another node and make sure it catches up.
- Group of 3 testers
- If smoke test passes, full release of the release candidate version is approved.
- If stress test fails, fix and update and release a new rc version and perform smoke test again.
- Once smoke test passes, and full version is released, bump versions in downstream components and re-publish happs, and initiate full testing. This includes the demo apps Talking Stickies and Kando.
- Once testing passes and persistent DHT is functional for the given time period and no bugs have been reported, elevate release to "recommended" status.
- Estimated time from a release candidate to smoke test results: 1 day
- Estimated time from release candidate smoke test passed to full release: 1-3 days
- Estimated time from full release to tested stable release: 10-16 days (1-2 weeks to bump versions on all tools and test, plus 2 days testing)