+ 1 to publish stable, "snapshot"-like releases from the Ratis
frequently For example a monthly patch release from the latest stable
branch.
Nanda had similar suggestion during the community meeting (Ozone should
depend on properly released patch releases from Ratis instead of snapshots).
I just shared the archive of the community call on the Ozone dev list
which includes the discussion.
One additional argument was that Ratis 1.1 branch is not something which
is ready to use, but it requires more work (triage / cherry-pick) which
has additional risk compared to using the already-tested Ratis master
(with disabled new features.)
Marton
On 2/2/21 7:45 PM, Attila Doroszlai wrote:
It is odd that 2.0 is expected to be more stable than 1.1 when 2.0 should
be a superset of 1.1.
My understanding is that current Ratis master (to become 2.0) is more
extensively tested in "production" via Ozone. Ratis 1.1 may be more
stable feature-wise, but there is an uncertainty factor because fixes
still need to be cherry-picked and integration tested.
In the future I think it would be better to establish a maintenance
branch from which snapshots could be released for Ozone. This would
let Ozone to take critical fixes in a timely manner without becoming
dependent on the in-development version including new API etc.
-Attila
