We in Apache CouchDB have just released v3.0.0, which introduces backwards-compatibility breaking changes. We also have v4.0.0 in the works.
We’d like to add the following tracks to our couchdb snap:
2.x
3.x
4.x
each with stable/candidate/beta/edge channels.
We’ll republish our current rev 5 release (the final 2.x) release onto the 2.x, put our new candidate 3.0.0 onto 3.x, and once 4.x is out, place it onto 4.x.
+1 from me on this request, seems consistent with semantics and use of tracks regarding backwards (in)compatibility and giving users the choice of an older version of the software.
How often do releases come out? Do you have a link to a document on release schedule/cadence? It’s very unlikely to affect my vote, just for completeness.
We’ll come back to tally votes in a few dates and action the rest of the request.