1. +1nb 2. +1nb 3. +1nb It’s been encouraging to follow discussion advancing potential enhancements to this proposal on the other threads.
I disagree that it is a good outcome for the project and the Apache Cassandra user community to veto significant progress in this area on grounds that the CEP does not contain a design for a feature that is a non-goal of the initial scope proposed by the CEP, and which is also not precluded by the CEP. - Scott > On Oct 14, 2021, at 11:27 AM, Aleksey Yeschenko <alek...@apache.org> wrote: > > +1 on all points > >> On 14 Oct 2021, at 17:31, bened...@apache.org wrote: >> Hi everyone, >> I would like to start a vote on this CEP, split into three sub-decisions, as >> discussion has been circular for some time. >> 1. Do you support adopting this CEP? >> 2. Do you support the transaction semantics proposed by the CEP for >> Cassandra? >> 3. Do you support an incremental approach to developing transactions in >> Cassandra, leaving scope for future development? >> The first vote is a consensus vote of all committers, the second and third >> however are about project direction and therefore are simple majority votes >> of the PMC. >> Recall that all -1 votes must be accompanied by an explanation. If you >> reject the CEP only on grounds (2) or (3) you should not veto the proposal. >> If a majority reject grounds (2) or (3) then transaction developments will >> halt for the time being. >> This vote will be open for 72 hours. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > For additional commands, e-mail: dev-h...@cassandra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
