+1 to moving v5-beta changes in trunk to new protocol v6. Regarding 3.11 and v5, I suppose we could say, v5 could never get matured beyond beta, but not sure if it would be confusing to see v6 while v5 is still in beta (curious on others' thoughts as well)
On Tue, Dec 8, 2020 at 12:33 PM Mick Semb Wever <m...@apache.org> wrote: > > …move to v6 for the new protocol to avoid this issue > > > +1, feels more the "grown-up thing to do". > > > > > Perhaps we should skip v5… > > We could finalise v5 as it was prior to the new framing format, then > create v6-beta in trunk only with the 15299 changes. > > > Would v5 come out of beta then in 3.11?, or would it stay as beta forever, > with the focus on maturing v6 in 4.0+? >
