Re: [DISCUSS] Modeling JIRA fix version for subprojects

Mick has filed a request to rename CASSANDRASC to CASSSIDECAR and to create CASSANALYTICS in https://issues.apache.org/jira/browse/INFRA-26276. Both projects are live now: https://issues.apache.org/jira/projects/CASSSIDECAR https://issues.apache.org/jira/projects/CASSANALYTICS Thanks again to Mic

Re: [DISCUSS] Modeling JIRA fix version for subprojects

Until someone creates a new design for them, I have changed them to "the eye" like the main project. Kind Regards, Brandon On Thu, Oct 24, 2024 at 5:27 PM Yifan Cai wrote: > > Thanks for working on this! > > Another bikeshed I noticed is the project logo. > > Currently, all of them share the sam

Re: [DISCUSS] Modeling JIRA fix version for subprojects

Thanks for working on this! Another bikeshed I noticed is the project logo. Currently, all of them share the same one as Sidecar. The subprojects can be styled up. :p - Yifan On Wed, Oct 23, 2024 at 9:46 AM Brandon Williams wrote: > https://issues.apache.org/jira/projects/CASSPYTHON/ > https

Re: [DISCUSS] Modeling JIRA fix version for subprojects

https://issues.apache.org/jira/projects/CASSPYTHON/ https://issues.apache.org/jira/projects/CASSJAVA/ https://issues.apache.org/jira/projects/CASSGO/ are now live. If you know of any issues to move there, please do so. Kind Regards, Brandon On Wed, Oct 23, 2024 at 6:59 AM Brandon Williams wrot

Re: [DISCUSS] Modeling JIRA fix version for subprojects

If nobody objects I will be creating the CASS jira projects later today. Kind Regards, Brandon On Tue, Oct 22, 2024 at 10:35 AM Ekaterina Dimitrova wrote: > > Honestly, counting the letters was also a thing that happened to me but I > should admit that even with CASSANDRAANALYTICS we count the

Re: [DISCUSS] Modeling JIRA fix version for subprojects

Honestly, counting the letters was also a thing that happened to me but I should admit that even with CASSANDRAANALYTICS we count the As… My preference is CASSX Seems shorter and less painful to read to me as a user. Thanks On Tue, 22 Oct 2024 at 11:18, Patrick McFadin wrote: > CASS + NAM

Re: [DISCUSS] Modeling JIRA fix version for subprojects

CASS + NAME is my +1 TBH rarely with this be typed. Just copied and pasted. It has to be clear that naming is different from the other projects and I think we get it either way. On Tue, Oct 22, 2024 at 8:15 AM Štefan Miklošovič wrote: > > Something like this? > > CASSANDRA > CASSPYTHON > CASSGO

Re: [DISCUSS] Modeling JIRA fix version for subprojects

That seems reasonable for me. On Tue, Oct 22, 2024 at 8:01 AM Brandon Williams wrote: > > I don't think underscore is an option from selfserve anyway. If we > have to stick everything together then I think having fewer things is > better, so we could drop the 'driver' and just name things like >

Re: [DISCUSS] Modeling JIRA fix version for subprojects

Something like this? CASSANDRA CASSPYTHON CASSGO CASSJAVA CASSSIDECAR CASSANALYTICS if we expand it would be like CASSANDRA CASSANDRAPYTHON CASSANDRAGO CASSANDRAJAVA CASSANDRASIDECAR CASSANDRAANALYTICS I don't know ... the first form seems fine to me but that triple S in CASSSIDECAR is strange.

Re: [DISCUSS] Modeling JIRA fix version for subprojects

I don't think underscore is an option from selfserve anyway. If we have to stick everything together then I think having fewer things is better, so we could drop the 'driver' and just name things like CASSPYTHON. WDYT? Kind Regards, Brandon On Tue, Oct 22, 2024 at 9:33 AM Štefan Miklošovič wro

Re: [DISCUSS] Modeling JIRA fix version for subprojects

So we will have stuff like CASS_DRIVER_PYTHON and all tickets in CHANGES.txt as well as in the commit messages will be like CASS_DRIVER_PYTHON-1234 I checked (1) and there is not a single one which has underscores in its name, now THAT would be a precedent, wouldn't it ... (1) https://issues.ap

Re: [DISCUSS] Modeling JIRA fix version for subprojects

This seems to be relevant documentation: https://confluence.atlassian.com/adminjiraserver/changing-the-project-key-format-938847081.html Martin -- This email, including attached files, may contain confidential information and is intended only for the use of the individual and/or entity to which

Re: [DISCUSS] Modeling JIRA fix version for subprojects

Well, I don't see any TLPs with anything but alphanumeric, and only one of those contains a number. Kind Regards, Brandon On Tue, Oct 22, 2024 at 9:12 AM Patrick McFadin wrote: > > I thought underscore was one of the allowed characters. Or it could be and > has just been restricted in the admin

Re: [DISCUSS] Modeling JIRA fix version for subprojects

I thought underscore was one of the allowed characters. Or it could be and has just been restricted in the admin regex. On Tue, Oct 22, 2024 at 6:53 AM Brandon Williams wrote: > It looks like I can create the subprojects myself with > https://selfserve.apache.org but there is a small issue with

Re: [DISCUSS] Modeling JIRA fix version for subprojects

It looks like I can create the subprojects myself with https://selfserve.apache.org but there is a small issue with the bikeshed: JIRA projects must be alphanumeric only. So we can have CASSDRIVERPYTHON but not CASS-DRIVER-PYTHON. I'm not a huge fan of everything stuck together like that, but may

Re: [DISCUSS] Modeling JIRA fix version for subprojects

Yeah +1 also to CASS-. I think it's widely understood in the community. On 2024/10/20 17:21:58 Jon Haddad wrote: > Agreed. I think everyone involved with cassandra will recognize CASS. > — > Jon Haddad > Rustyrazorblade Consulting > rustyrazorblade.com > > > On Sun, Oct 20, 2024 at 7:18 AM J

Re: [DISCUSS] Modeling JIRA fix version for subprojects

Agreed. I think everyone involved with cassandra will recognize CASS. — Jon Haddad Rustyrazorblade Consulting rustyrazorblade.com On Sun, Oct 20, 2024 at 7:18 AM Josh McKenzie wrote: > +1 to CASS- shorthand. > > Think you're going to just have to agree to disagree on this one Stefan; > clea

Re: [DISCUSS] Modeling JIRA fix version for subprojects

+1 to CASS- shorthand. Think you're going to just have to agree to disagree on this one Stefan; clear majority consensus on it on this thread afaict. On Sat, Oct 19, 2024, at 8:55 AM, Mick Semb Wever wrote: >> Isn't it weird that you said that we should not save characters at the cost >> of

Re: [DISCUSS] Modeling JIRA fix version for subprojects

> > Isn't it weird that you said that we should not save characters at the > cost of readability while we just use CASS everywhere except the main > project? Why do you think that having "CASS-" will make people > automatically think that this is Cassandra related. No other project in > Apache (afa

Re: [DISCUSS] Modeling JIRA fix version for subprojects

Third time's the charm. In case somebody got I wrong, I want to correct myself. I wrote "Right ... I got it" at the end, what I meant by that is that I actually don't. My point is that if we are after readability, we should not shorten the project name itself. It is inconsistent with CASSANDRA,

Re: [DISCUSS] Modeling JIRA fix version for subprojects

That is good to know. My preference would be moving the driver projects and analytics first, and renaming the sidecar project later. However, if it is not a concern, I am fine with doing the change in bulk, especially if it is more convenient. - Yifan On Fri, Oct 18, 2024 at 11:24 AM Jon Haddad

Re: [DISCUSS] Modeling JIRA fix version for subprojects

I think that this: CASS-ANALYTICS is actually worse than this CASSANDRA-ANA (or any variation of that). I would just expand CASS to CASSANDRA everywhere, if we dont, then you are trying to say that this CASSANDRA-ANALYTICS is just too long, but this CASS-ANALYTICS isn't. Right ... got it.

Re: [DISCUSS] Modeling JIRA fix version for subprojects

I'm 95% sure it redirects automatically. I believe those redirects also work when moving issues from one project to another, so when we move all the driver issues to their own repos everything should keep working. On Fri, Oct 18, 2024 at 11:21 AM Francisco Guerrero wrote: > This is one thing

Re: [DISCUSS] Modeling JIRA fix version for subprojects

So we will have: CASSANDRA CASS-DRIVER-JAVA CASS-DRIVER-GO CASS-ANALYTICS CASS-SIDECAR Isn't it weird that you said that we should not save characters at the cost of readability while we just use CASS everywhere except the main project? Why do you think that having "CASS-" will make people a

Re: [DISCUSS] Modeling JIRA fix version for subprojects

Anyone know if there are any traps when renaming a JIRA project? Since we are talking about change CASSANDRASC to CASS-SIDECAR. - Yifan On Fri, Oct 18, 2024 at 10:50 AM Patrick McFadin wrote: > Awesome. Now this is the bikeshedding I'm here for. :popcorn: > > On Fri, Oct 18, 2024 at 5:26 AM Br

Re: [DISCUSS] Modeling JIRA fix version for subprojects

This is one thing that comes to mind. All of the commits in Sidecar have a reference to the JIRA, if we switch it from CASSANDRASC -> CASS-SIDECAR, will there he redirection of these tickets? Or will be lose those links and the ability to automatically refer to the JIRAs? On 2024/10/18 18:17:16 Y

Re: [DISCUSS] Modeling JIRA fix version for subprojects

Awesome. Now this is the bikeshedding I'm here for. :popcorn: On Fri, Oct 18, 2024 at 5:26 AM Brandon Williams wrote: > I think for the sidecar we need the dash to avoid the typo-likely > 'SSS' wart. I have updated INFRA-26212 to follow CASS-DRIVER-. > > Kind Regards, > Brandon > > On Fri, Oct 1

Re: [DISCUSS] Modeling JIRA fix version for subprojects

I think for the sidecar we need the dash to avoid the typo-likely 'SSS' wart. I have updated INFRA-26212 to follow CASS-DRIVER-. Kind Regards, Brandon On Fri, Oct 18, 2024 at 4:55 AM Mick Semb Wever wrote: > > Could we also rename CASSANDRASC to CASSSIDECAR ? > > And tbh, i'd much rather CASS-DR

Re: [DISCUSS] Modeling JIRA fix version for subprojects

+1 to Mick’s suggestion CASS-DRIVER- / CASS-SIDECAR / CASS-ANALYTICS, this feels more consistent and readable than without the dash. Also -1 to CASSANA fwiw, sorry Stefan 😅 /bikeshed On Fri, 18 Oct 2024 at 05:55 Mick Semb Wever wrote: > Could we also rename CASSANDRASC to CASSSIDECAR ? > > And

Re: [DISCUSS] Modeling JIRA fix version for subprojects

Could we also rename CASSANDRASC to CASSSIDECAR ? And tbh, i'd much rather CASS-DRIVER-, CASS-ANALYTICS and CASS-SIDECAR (but ofc it's not really important) On Thu, 17 Oct 2024 at 23:11, Štefan Miklošovič wrote: > Interesting, adding "-ana" suffix to a dc which is meant to be an > analytical

Re: [DISCUSS] Modeling JIRA fix version for subprojects

Interesting, adding "-ana" suffix to a dc which is meant to be an analytical one was pretty common in cases I saw. People just want to look at it and see the difference, how do they name it then? dc2? Also, omitting 2 letters does not seem like a typo to me either. Anyway, we are clearly after th

Re: [DISCUSS] Modeling JIRA fix version for subprojects

I'm with Jon here, -1 to CASSANA and +1 to CASSANALYTICS. Kind Regards, Brandon On Thu, Oct 17, 2024 at 4:00 PM Jon Haddad wrote: > > +1 to CASSANALYTICS > > a fierce -1 to CASSANA. I’ve never once in my life seen this convention and > id prefer clarity over saving a handful of characters. > >

Re: [DISCUSS] Modeling JIRA fix version for subprojects

+1 to CASSANALYTICS a fierce -1 to CASSANA. I’ve never once in my life seen this convention and id prefer clarity over saving a handful of characters. — Jon Haddad Rustyrazorblade Consulting rustyrazorblade.com On Thu, Oct 17, 2024 at 1:57 PM Štefan Miklošovič wrote: > CASSANA would do it. CA

Re: [DISCUSS] Modeling JIRA fix version for subprojects

> CASSANA would do it. CASSANALYTICS is just too long. People are used to the > terminology of "ana" e.g. when naming their analytics data centers. CASSANA looks like a "Cassandra" typo to me. But naming is hard, so let's see if others have an opinion about this. On 2024/10/17 20:57:29 Štefan Mik

Re: [DISCUSS] Modeling JIRA fix version for subprojects

CASSANA would do it. CASSANALYTICS is just too long. People are used to the terminology of "ana" e.g. when naming their analytics data centers. On Thu, Oct 17, 2024 at 2:55 PM Bernardo Botella < conta...@bernardobotella.com> wrote: > +1 to CASSANALYTICS > > On Oct 17, 2024, at 1:48 PM, Yifan Cai

Re: [DISCUSS] Modeling JIRA fix version for subprojects

+1 to CASSANALYTICS > On Oct 17, 2024, at 1:48 PM, Yifan Cai wrote: > > yep. CASSANALYTICS sounds good to me. +1 > > On Thu, Oct 17, 2024 at 1:45 PM Francisco Guerrero > wrote: >> > Can we include Cassandra Analytics to the infra ticket? I am looking >> > forward to

Re: [DISCUSS] Modeling JIRA fix version for subprojects

yep. CASSANALYTICS sounds good to me. +1 On Thu, Oct 17, 2024 at 1:45 PM Francisco Guerrero wrote: > > Can we include Cassandra Analytics to the infra ticket? I am looking > > forward to jira project name suggestions for it... > > How about CASSANALYTICS ? > > On 2024/10/17 18:50:45 Yifan Cai wr

Re: [DISCUSS] Modeling JIRA fix version for subprojects

> Can we include Cassandra Analytics to the infra ticket? I am looking > forward to jira project name suggestions for it... How about CASSANALYTICS ? On 2024/10/17 18:50:45 Yifan Cai wrote: > Can we include Cassandra Analytics to the infra ticket? I am looking > forward to jira project name sugge

Re: [DISCUSS] Modeling JIRA fix version for subprojects

Can we include Cassandra Analytics to the infra ticket? I am looking forward to jira project name suggestions for it... - Yifan On Thu, Oct 17, 2024 at 10:46 AM Patrick McFadin wrote: > I think it needs a bit more blue. Maybe some pink stripes. I'll file a > Jira. > > On Thu, Oct 17, 2024 at 9:

Re: [DISCUSS] Modeling JIRA fix version for subprojects

I think it needs a bit more blue. Maybe some pink stripes. I'll file a Jira. On Thu, Oct 17, 2024 at 9:01 AM Brandon Williams wrote: > Thanks everyone, I've created > https://issues.apache.org/jira/browse/INFRA-26212 > > Kind Regards, > Brandon > > On Thu, Oct 17, 2024 at 9:55 AM Ekaterina Dimit

Re: [DISCUSS] Modeling JIRA fix version for subprojects

Thanks everyone, I've created https://issues.apache.org/jira/browse/INFRA-26212 Kind Regards, Brandon On Thu, Oct 17, 2024 at 9:55 AM Ekaterina Dimitrova wrote: > > It would have been nice to be in red italic but… :-) > > Thanks, Brandon, +1 to the suggestion on my end too. Sounds reasonable to

Re: [DISCUSS] Modeling JIRA fix version for subprojects

It would have been nice to be in red italic but… :-) Thanks, Brandon, +1 to the suggestion on my end too. Sounds reasonable to me On Thu, 17 Oct 2024 at 17:50, Abe Ratnofsky wrote: > +1 to CASSDRIVER-JAVA et al. > > On Oct 17, 2024, at 10:37 AM, Jon Haddad wrote: > > Sgtm, let’s ship it > > +

Re: [DISCUSS] Modeling JIRA fix version for subprojects

+1 to CASSDRIVER-JAVA et al. > On Oct 17, 2024, at 10:37 AM, Jon Haddad wrote: > > Sgtm, let’s ship it > > +1 > > > > On Thu, Oct 17, 2024 at 4:09 AM Brandon Williams > wrote: >> Nobody wants to suggest a color for this bikeshed? I'll start: >> CASSDRIVER-. I'd lik

Re: [DISCUSS] Modeling JIRA fix version for subprojects

Sgtm, let’s ship it +1 On Thu, Oct 17, 2024 at 4:09 AM Brandon Williams wrote: > Nobody wants to suggest a color for this bikeshed? I'll start: > CASSDRIVER-. I'd like to get on this sooner than later since > during the time we wait the situation worsens. > > Kind Regards, > Brandon > > On W

Re: [DISCUSS] Modeling JIRA fix version for subprojects

Nobody wants to suggest a color for this bikeshed? I'll start: CASSDRIVER-. I'd like to get on this sooner than later since during the time we wait the situation worsens. Kind Regards, Brandon On Wed, Oct 2, 2024 at 5:07 PM Brandon Williams wrote: > > I think we just need to ask infra to create

Re: [DISCUSS] Modeling JIRA fix version for subprojects

I think we just need to ask infra to create the jira instances, but I guess we need to have some kind of consistent naming scheme to help identify them? Kind Regards, Brandon On Wed, Oct 2, 2024 at 1:02 PM Francisco Guerrero wrote: > > +1 too on the points brought by Mick, we need more visibilit

Re: [DISCUSS] Modeling JIRA fix version for subprojects

+1 too on the points brought by Mick, we need more visibility into subprojects. For starters, we should look into integrating Qbot notifications in #cassandra-dev and #cassandra-noise for CASSANDRASC tickets. Let me know if I can help with that. On 2024/10/02 17:39:28 Yifan Cai wrote: > +1 on all

Re: [DISCUSS] Modeling JIRA fix version for subprojects

+1 on all the points raised by Mick. Please let me know if there is anything I can help with. - Yifan On Wed, Oct 2, 2024 at 8:13 AM Josh McKenzie wrote: > - Qbot notifications in #cassandra-dev and #cassandra-noise , as well as > in any subproject channels > - some cadence of dev@ ML updates,

Re: [DISCUSS] Modeling JIRA fix version for subprojects

> - Qbot notifications in #cassandra-dev and #cassandra-noise , as well as in > any subproject channels > - some cadence of dev@ ML updates, e.g. on activities, or dependency changes, > etc > - regular releases Agree on all 3 points. Also - I've *definitely* fallen off on the project updates for

Re: [DISCUSS] Modeling JIRA fix version for subprojects

To play devil's advocate here, it's important that the subprojects don't lose visibility and silo from the rest of the project. There are different ways to solve this, and lumping everything into one jira project is a messy and poor way of doing it. But as the sidecar has shown us, subproject act

Re: [DISCUSS] Modeling JIRA fix version for subprojects

Also, many Jira reports are based off Jira projects. So mixing everything in one bag makes those unusable. But more importantly future Jira features/integrations/etc will probably be project oriented as well and they might become difficult or unusable to us. My 2cts. On 1/10/24 23:44, Yifan

Re: [DISCUSS] Modeling JIRA fix version for subprojects

I support the idea of having separate Jira projects. Based on my experience with both shared namespaces (like Cassandra and Analytics) and dedicated namespaces (like Sidecar), I've seen the drawbacks of grouping all subproject tickets under a single project, i.e. Cassandra. When tickets are consol

Re: [DISCUSS] Modeling JIRA fix version for subprojects

What is the status of this thread? Are we looking to move each driver project to its own jira instance, as voted for in CEP-8? Kind Regards, Brandon On Tue, Apr 9, 2024 at 9:29 AM Brandon Williams wrote: > > I am +1 on separate projects as well, but to Abe's point I don't think > it matters now,

Re: [DISCUSS] Modeling JIRA fix version for subprojects

CEP-8 says "We suggest distinct Jira projects, one per driver, all to be created." Kind Regards, Brandon On Tue, Oct 1, 2024 at 9:23 AM Jon Haddad wrote: > > My 2 cents - trying to look through C* JIRA right now is kind of awful with > different projects all mixed in. Given that the decision t

Re: [DISCUSS] Modeling JIRA fix version for subprojects

My 2 cents - trying to look through C* JIRA right now is kind of awful with different projects all mixed in. Given that the decision to lump everything together seems to have been made unilaterally, against the VOTE, I'd say we still need to move drivers off CASSANDRA. Only question is, one for a

Re: [DISCUSS] Modeling JIRA fix version for subprojects

I am +1 on separate projects as well, but to Abe's point I don't think it matters now, we had 21 binding votes for CEP-8 which spells this out. Kind Regards, Brandon On Tue, Apr 9, 2024 at 9:24 AM Josh McKenzie wrote: > > +1 to separate JIRA projects per subproject. Having workflows distinct to

Re: [DISCUSS] Modeling JIRA fix version for subprojects

+1 to separate JIRA projects per subproject. Having workflows distinct to each project is reason enough for me, nevermind the global namespace pollution that occurs if you pack a bunch of disparate projects together into one instance. On Mon, Apr 8, 2024, at 9:11 PM, Dinesh Joshi wrote: > hi fol

Re: [DISCUSS] Modeling JIRA fix version for subprojects

hi folks - sorry to have dropped the ball on responding to this thread. My 2 cents are as follows - 1. Having a separate JIRA project for each sub-project will add management overhead. This option, however, allows us to model unique workflows for the sub-project. 2. Managing the sub-project as p

Re: [DISCUSS] Modeling JIRA fix version for subprojects

CEP-8 proposes using separate Jira projects per Cassandra sub-project: https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-8%3A+DataStax+Drivers+Donation > We suggest distinct Jira projects, one per driver, all to be created. I don't see any discussion changing that from the [DISCUSS] or vo

Re: [DISCUSS] Modeling JIRA fix version for subprojects

Imo it would be better to have standalone JIRA projects for each of the subprojects we have, just like we do the sidecar. On Thu, Apr 4, 2024 at 10:47 AM Francisco Guerrero wrote: > Hi Bret, > > Thanks for bringing up this issue. The Cassandra Analytics library will > also need to have its own v

Re: [DISCUSS] Modeling JIRA fix version for subprojects

Hi Bret, Thanks for bringing up this issue. The Cassandra Analytics library will also need to have its own versioning. We should align on version naming for subprojects and start using it for both the Java Driver and the Analytics library. I propose the following versioning "java-driver-${version

[DISCUSS] Modeling JIRA fix version for subprojects

Greetings all! For those I haven't met yet I'm Bret and I'm working mainly on the newly-donated Java driver. As part of that effort we've hit upon an issue that we felt needed some additional discussion... and so you now have an email from me. :) Our JIRA instance currently has a single fi