prefer to merge
sooner than later, if there’s no particular reason to delay.
From: Stefan Miklosovic
Date: Tuesday, 28 September 2021 at 13:52
To: dev@cassandra.apache.org
Subject: Re: [DISCUSS] CASSANDRA-16922 CEP-10: Major Prerequisites (Phase 1)
Hi Benedict,
do I need to somehow accommodate
er phases are being posted now as well, with the
> Simulator itself to follow this week.
>
>
> From: Joshua McKenzie
> Date: Friday, 17 September 2021 at 22:08
> To: dev@cassandra.apache.org
> Subject: Re: [DISCUSS] CASSANDRA-16922 CEP-10: Major Prerequisites (Phase 1)
> >
&g
Subject: Re: [DISCUSS] CASSANDRA-16922 CEP-10: Major Prerequisites (Phase 1)
>
> ideally if feature development is expected to span more than a single
> quarter it would be best to target phased incorporation into mainline
Strong +1 here. Ariel was right. :)
On Fri, Sep 17, 2021 at 4:47 PM
> >> incorporation into mainline, and not defer everything to the final
> moment.
> >> I think it also helps focus review, testing, documentation etc. to have
> >> manageable chunks of work merged long before any perceived deadline.
> >>
> >>
> >>
ation etc. to have
>> manageable chunks of work merged long before any perceived deadline.
>>
>>
>> From: Jeremiah D Jordan
>> Date: Friday, 17 September 2021 at 20:50
>> To: Cassandra DEV
>> Subject: Re: [DISCUSS] CASSANDRA-16922 CEP-10: Major Prereq
ed deadline.
>
>
> From: Jeremiah D Jordan
> Date: Friday, 17 September 2021 at 20:50
> To: Cassandra DEV
> Subject: Re: [DISCUSS] CASSANDRA-16922 CEP-10: Major Prerequisites (Phase
> 1)
> > As these progress through review, the aim is to roll them up into a
> single
at 20:50
To: Cassandra DEV
Subject: Re: [DISCUSS] CASSANDRA-16922 CEP-10: Major Prerequisites (Phase 1)
> As these progress through review, the aim is to roll them up into a single
> branch and merge that to trunk together, keeping the separate commits for the
> specific JIRAs.
On Fri, Sep 17, 2021 at 2:50 PM Jeremiah D Jordan
wrote:
> I think this is a great idea. Where do you see the “Roll Up Branch” living?
> Does the project want to start keeping long lived feature branches in the
> apache/cassandra repository? Or should the roll up branch still be kept in a
>
> As these progress through review, the aim is to roll them up into a single
> branch and merge that to trunk together, keeping the separate commits for the
> specific JIRAs.
I think this is a great idea. Where do you see the “Roll Up Branch” living?
Does the project want to start keeping
This umbrella issue covers the major structural refactorings to enable the
higher level pieces of CEP-10. The current proposal is to post separate patches
for each JIRA to lessen the review burden as much as possible. However, the
patches are incremental, so there is a dependency from one to
10 matches
Mail list logo
