Re: GoCQL module name change and next release

2024-10-15 Thread João Reis
urely help. Low hanging fruit should also not be a problem for > me to review. > > Are we looking to review/triaging all existing PRs? > > Thanks, > > Carlos > -- > *From:* João Reis > *Sent:* 11 October 2024 16:03 > *To:* dev@cassandra.ap

Re: GoCQL module name change and next release

2024-10-14 Thread Rolo, Carlos via dev
oking to review/triaging all existing PRs? Thanks, Carlos From: João Reis Sent: 11 October 2024 16:03 To: dev@cassandra.apache.org Subject: Re: GoCQL module name change and next release You don't often get email from joaor...@apache.org. Learn why this is

Re: GoCQL module name change and next release

2024-10-11 Thread João Reis
I like that too, I initially considered proposing that but thought I'd propose delivering v5 and vector support faster but +1 on making these two features a part of 2.0.0 instead. Štefan Miklošovič escreveu (quinta, 10/10/2024 à(s) 23:37): > I would do 1) and 2) together. I would rename the modu

Re: GoCQL module name change and next release

2024-10-10 Thread Štefan Miklošovič
I would do 1) and 2) together. I would rename the module in 2.0.0 and there would be v5 and vector support as well. It would motivate us to get v5 and vector out while using that opportunity to rename it to 2.0.0. On Thu, Oct 10, 2024 at 11:42 AM João Reis wrote: > Hi, > > Following the GoCQL do

GoCQL module name change and next release

2024-10-10 Thread João Reis
Hi, Following the GoCQL donation we need to change the module name so it matches the new repo URL. Currently users have to keep using the old name unless they add a rewrite to go.mod. There was a discussion on what the approach should be on #1776 [1] and I've created CASSANDRA-19993 [2] to track