Re: [DISCUSS] Allow UPDATE on settings virtual table to change running configuration

2023-02-28 Thread Ekaterina Dimitrova
I agree with David that the annotations seem a bit too many but if I have to choose from the three approaches - the annotations one seems most reasonable to me and I didn’t have the chance to consider any others. Volatile seems fragile and unclear as a differentiator. I agree On Tue, 28 Feb 2023 a

Re: [DISCUSS] Next release date

2023-02-28 Thread C. Scott Andreas
Regarding “We should focus on why it took 6 months to go from 4.1 first alpha to GA and what happened inside that time window.” —Speaking solely from my perspective, the single biggest time draw was tracking down and resolving https://issues.apache.org/jira/browse/CASSANDRA-18110.One of the strateg

Re: [DISCUSS] Allow UPDATE on settings virtual table to change running configuration

2023-02-28 Thread Maxim Muzafarov
Folks, If there are no objections to the approach described in this thread, I'd like to proceed with this change. The change seems to be valuable for the upcoming release, so any comments are really appreciated. On Wed, 22 Feb 2023 at 21:51, David Capwell wrote: > > I guess back to the point of

Re: [DISCUSS] Next release date

2023-02-28 Thread Benedict
I agree, we shouldn’t be branching annually, we should be releasing annually - and we shouldn’t assume that will take six months. We should be aiming for 1-2mo and so long as our trajectory towards that is good, I don’t think there’s anything to worry about (and we’ll get our first comparative data

Re: [DISCUSS] Next release date

2023-02-28 Thread Ekaterina Dimitrova
By “not to have to delay again” I mean GA, not the agreement for when to branch and start feature freeze. Just to be clear as I realized I might be misunderstood :-) On Tue, 28 Feb 2023 at 10:47, Ekaterina Dimitrova wrote: > I agree that November-May falls too short so +1 on postponing the day o

Re: [DISCUSS] Next release date

2023-02-28 Thread Ekaterina Dimitrova
I agree that November-May falls too short so +1 on postponing the day on my end Now I think Mick brought excellent point - let’s get into separate discussion about the root cause of releasing 4.1 only in December and see what we need to change/improve on so we do not get into future delays and we

Re: [DISCUSS] Next release date

2023-02-28 Thread Mick Semb Wever
> > We forked the 4.0 and 4.1 branches beginning of May. Unfortunately, for > 4.1 we were only able to release GA in December which impacted how much > time we could spend focussing on the next release and the progress that we > could do. By consequence, I am wondering if it makes sense for us to b

Re: [DISCUSS] Next release date

2023-02-28 Thread J. D. Jordan
I think it makes sense to plan on cutting the branch later given when 4.1 actually released. I would suggest either August or September as a good time to cut the branch, at the end of the summer. -Jeremiah > On Feb 28, 2023, at 7:42 AM, Benjamin Lerer wrote: > >  > Hi, > > We forked the 4.0

[DISCUSS] Next release date

2023-02-28 Thread Benjamin Lerer
Hi, We forked the 4.0 and 4.1 branches beginning of May. Unfortunately, for 4.1 we were only able to release GA in December which impacted how much time we could spend focussing on the next release and the progress that we could do. By consequence, I am wondering if it makes sense for us to branch

Re: A Guest invitation to the Slack Dev Community

2023-02-28 Thread Mick Semb Wever
Invite sent to you. On Tue, 28 Feb 2023 at 08:51, Maxim Chanturiay wrote: > Hello! > > I would like to join slack dev community, as a guest. > My current email address is the one I'd like to use. > > If it is of any help, here's a link to my ASF Jira Account: > https://issues.apache.org/jira/sec