Count of tasks, known to be required to progress towards a final release 2.9.0 of Riak. The release phase is split into four parts:
-
Private Release Candidate - preparing a branch which can be subject to non-production testing by the primary Riak customers involved in the development cycle. This will allow for further testing under different constraints, and work to commence on exploiting the required features.
-
Public Release Candidate - provide a release candidate that has passed sufficient testing to allow for proving in non-production environments by a broader customer base.
-
Release 2.9.0 - a quality-assured first release of the series.
-
Subsequent Releases - any features deferred from 2.9.0, or fixes discovered post the Release of 2.9.0 may lead to subsequent releases.
Task | Status |
---|---|
Complete first round of riak functional test | complete - mas |
Risk assessment following riak functional test | complete - mas |
Confirm eqc tests | complete - rdb |
Merge in hot_backup work and test | complete - mas |
Configuration guidance for exposed Leveled and Tictac AAE features | complete - mas |
Tagged release of leveled and kv_index_tictactree repos |
complete - mas |
Provide preview of overview notes for release | complete - mas |
Final test before declaring private RC ready | complete - mas |
To access the private release candidate use the branch develop-2.9.0-PRC0
after cloning the riak repo at https://github.com/martinsumner/riak.git
. Locked dependencies should NOT be used - use make deps
followed by make rel
to build.
Task | Status |
---|---|
Add enterprise leveldb into the build for Riak (with hot backup feature) | complete - mas |
Creation of actual develop 2.9 branch | complete - mas |
Tag release candidate (runs from make locked-deps) | unassigned |
Code and test review of get_fsm changes | complete - rdb |
Volume test showing bitcask comparison (not just leveled vs leveldb) | complete - mas |
Testing in more live-like Spine environment (with larger disks) | ongoing - nhs |
Testing in more live-like SuS environment | pending - nhs |
Completion of HTTP API for Cluster-wide AAE | complete - rdb |
Verify previous volume test results on actual release candidate | ongoing - mas |
Two rounds of riak functional test on actual release candidate | ongoing - mas |
Compatibility testing with Riak CS (note that there is no support within 'prefix_multi' backend for leveled at present) | out-of-scope |
Publish preview of release notes | pending - TI Tokyo |
Leveled configuration when in multi-backend mode | complete - mas |
Leveled snapshot timeouts investigation | complete - mas |
Multi-backend testing | out-of-scope |
Task | Status |
---|---|
Additional independent property-based testing of leveled (focused on file-management actors) | ongoing - quviq |
Publication of release notes and documentation updates | unassigned |
Acceptance of PRs into basho repo | complete - mas |
Writing of migration guidance, with publication of volume test results for migration | pending - mas |
Review long-standing doc issues (e.g. term_regex, bitcask sync support, 2i non-recommendation) | unassigned |
Investigate issue with HTTP header limit following mochiweb change from self-parsing | complete - mas |
Attempt to recreate 2.0.5 to 2.9.0 stuck startup issue | complete rs |
The main focus after release 2.9.0 will shift to Release 3.0. The focus for Release 3.0 will be on OTP uplift and rebar3 compatibility. There are some features which were de-prioritised during the 2.2.5 and 2.9.0 release cycles, which may yet reemerge as candidate features for 2.9.x releases:
Task | Status |
---|---|
Revisit coordinator only flushes - previously when testing this didn't consider handoffs | unassigned |
Revisit non-primary read-repair | unassigned |
Add re-replicate if clock advanced feature (so clock returned from aae_fold can remain opaque to client) | unassigned |
Investigate Yokozuna abstraction PR | unassigned |
A-D replication fixes | ongoing - bet365 |