With 4.x remaining unstable in our "Q2" release, does that remove our reasoning for cutting a major release?
What will happen for the Q3 release when the 4.x TO API is ready? Will we want to cut another 8.x major release? <individual hat> I am all for making progress to remove deprecated codes, but for many users (myself included), major releases present a large investment in effort to adopt. I think the 1, maybe 2 major release per year cadence is reasonable. Three or more major releases in a year would be rather difficult to accommodate. --Eric On Tue, Feb 15, 2022 at 11:28 AM Taylor Frey <taylor.f...@gmail.com> wrote: > > 1. Attendance: > Srijeet Chatterjee > Eric Holguin > Steve Hamrick > Taylor Frey > Justin Howard > > 2. Official Release: > - TC 7.0.0 > - Officially remove TO 2.x / Riak > - Ansible currently uses 2, needs to finalize upgrade to 3 w/ testing > - TO API 4.x will remain unstable for this release given the 'in > development' progress of a few items > > On Tue, Feb 8, 2022 at 10:18 AM ocket 8888 <ocket8...@gmail.com> wrote: > > > If you have anything you want to discuss at next week's meeting, > > respond to this email and it's on the agenda. > >
