> to 4.0 and up to trunk
Think the proposal is all supported branches from 4.0 up.
+1 here.
On Mon, Oct 23, 2023, at 10:19 PM, guo Maxwell wrote:
> +1, but I want to know why only trunk and 4.0 ? not all the versions
> involved, like 4.1 ,5.0 。
>
> Francisco Guerrero 于2023年10月24日周二 07:47写道：
>>
My biggest concern with the 5.1 suggestion is that it makes the review of
TCM far more complicated than it should be. Even if all TCM patches were
fully reviewed by committers that I fully trust, due to the patch size and
the impact of the changes it feels safer to me to have a second round of
revi
On Tue, 24 Oct 2023 at 12:25, Benjamin Lerer wrote:
> My biggest concern with the 5.1 suggestion is that it makes the review of
> TCM far more complicated than it should be. Even if all TCM patches were
> fully reviewed by committers that I fully trust, due to the patch size and
> the impact of t
I am working on https://issues.apache.org/jira/browse/CASSANDRA-16565 and
have a small testing program that executes the sigar and equivalent OSHI
methods to verify that they are the same. I would like to have this run on
various platforms.
I have tgz with all the libraries and code as well as a
The concern I have with this is that is a big slippery 'if' that
involves development time estimation, and if it tends to take longer
than we estimate (as these things tend to do), then I can see a future
where 5.0 is delayed until the middle of 2024, and I really don't want
that to happen. Maybe
> Maybe it won't be a glamorous release but shipping
> 5.0 mitigates our worst case scenario.
I disagree with this characterization of 5.0 personally. UCS, SAI, Trie
memtables and sstables, maybe vector ANN if the sub-tasks on C-18715 are
accurate, all combine to make 5.0 a pretty glamorous relea
On Tue, Oct 24, 2023 at 7:48 AM Claude Warren, Jr via dev
wrote:
>
> Is there someplace I can stash the tgz that others can download it from? The
> file info is : 6269066 okt 24 12:46 compare_oshi_sigar.tgz
Is posting a github branch not sufficient?
On Tue, Oct 24, 2023 at 9:23 AM Josh McKenzie wrote:
> Maybe it won't be a glamorous release but shipping
> 5.0 mitigates our worst case scenario.
>
> I disagree with this characterization of 5.0 personally. UCS, SAI, Trie
> memtables and sstables, maybe vector ANN if the sub-tasks on C-18715 are
I understood that the intention is for this to land in 4.0 all the way up to
trunk (including 4.1 and 5.0).
On 2023/10/24 02:19:41 guo Maxwell wrote:
> +1, but I want to know why only trunk and 4.0 ? not all the versions
> involved, like 4.1 ,5.0 。
>
> Francisco Guerrero 于2023年10月24日周二 07:47写道：
+1
Kind Regards,
Brandon
On Mon, Oct 23, 2023 at 6:22 PM Yifan Cai wrote:
>
> Hi,
>
> I want to propose merging the patch in CASSANDRA-18941 to 4.0 and up to trunk
> and hope we are all OK with it.
>
> In CASSANDRA-18941, I am adding the capability to produce size-bounded
> SSTables in CQLSSTa
+1 to what you are saying, Josh. Based on the last survey, yes, everyone
was excited about Accord, but SAI and UCS were pretty high on the list.
Benedict and I had a good conversation last night, and now I understand
more essential details for this conversation. TCM is taking far more work
than in
I guess at the end of the day, shipping a release with a bunch of awesome
features is better than holding it back. If there's 2 big releases in 6 months
the community isn't any worse off.
We either ship something, or nothing, and something is probably better.
Jon
On 2023/10/24 16:27:04 Pat
If we decide to go the route of not merging TCM to the 5.0 branch. Do we
actually need to immediately cut a 5.1 branch? Can we work on stabilizing
things while it is in trunk and cut the 5.1 branch when we actually think
we are near releasing? I don’t see any reason we can not cut “preview”
art
I would like to have something for developers to use ASAP to try the Accord
syntax. Very few people have seen it, and I think there's a learning curve
we can start earlier.
It's my understanding that ASF policy is that it needs to be a project
release to create a docker image.
On Tue, Oct 24, 202
In order for the project to advertise the release outside the dev@ list it
needs to be a formal release. That just means that there was a release
vote and at least 3 PMC members +1’ed it, and there are more +1 than there
are -1, and we follow all the normal release rules. The ASF release
process
> In order for the project to advertise the release outside the dev@ list it
> needs to be a formal release.
That's my reading as well:
https://www.apache.org/legal/release-policy.html#release-definition
I wonder if there'd be value in us having a cronned job that'd do nightly
docker container b
Let me make that really easy. Hell yes
Not everybody runs CCM, I've tried but I've met resistance.
Compiling your own version usually involves me saying the words "Yes, ant
realclean exists. I'm not trolling you"
docker pull works on every OS and curates a single node experience.
On Tue, Oct
+1
On Tue, Oct 24, 2023 at 11:24 AM Brandon Williams wrote:
> +1
>
> Kind Regards,
> Brandon
>
> On Mon, Oct 23, 2023 at 6:22 PM Yifan Cai wrote:
> >
> > Hi,
> >
> > I want to propose merging the patch in CASSANDRA-18941 to 4.0 and up to
> trunk and hope we are all OK with it.
> >
> > In CASSAN
I'm certainly a fan of docker images as a dev tool! LorinaSent from my Verizon,
Samsung Galaxy smartphone
Original message From: Patrick McFadin
Date: 10/24/23 13:31 (GMT-08:00) To: dev@cassandra.apache.org Subject: Re:
Push TCM (CEP-21) and Accord (CEP-15) to 5.1 (and cut an
The catch here is that we don't publish docker images currently. The
C* docker images available are not made by us.
Kind Regards,
Brandon
On Tue, Oct 24, 2023 at 3:31 PM Patrick McFadin wrote:
>
> Let me make that really easy. Hell yes
>
> Not everybody runs CCM, I've tried but I've met resista
[LEGAL-656] Application of Generative AI policy to dependencies - ASF JIRAissues.apache.orgLegal’s opinion is that this is not an acceptable workaround to the policy.On 22 Sep 2023, at 23:51, German Eichberger via dev wrote:
+1 with taking it to legal
As anyone else I enjoy speculating
I sat down to add IR messages to the mix… given how positive the feedback was
for other repair messages I assume people are still ok with this new IR work
going to 5.0 as well, if not please let me know here (will send a patch
tomorrow).
Once I send out the patch 100% of repair messages have re
😄
Chris Lohfink 于2023年10月25日周三 05:02写道：
> +1
>
> On Tue, Oct 24, 2023 at 11:24 AM Brandon Williams
> wrote:
>
>> +1
>>
>> Kind Regards,
>> Brandon
>>
>> On Mon, Oct 23, 2023 at 6:22 PM Yifan Cai wrote:
>> >
>> > Hi,
>> >
>> > I want to propose merging the patch in CASSANDRA-18941 to 4.0 and up
I also think there's many good new features in 5.0 already they'd make a
good release even on their own. My 2 cts.
On 24/10/23 23:20, Brandon Williams wrote:
The catch here is that we don't publish docker images currently. The
C* docker images available are not made by us.
Kind Regards,
Brand
24 matches
Mail list logo
