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 consolidated in one project, visibility suffers. For instance, tickets must have a prefix in their titles, like in this example: https://issues.apache.org/jira/browse/CASSANDRA-19927. It's not immediately clear that this ticket pertains to the Analytics subproject without clicking the link. Additionally, using just the Cassandra project leads to project metadata—such as "components" and "labels"—that may not apply to other subprojects. This can create confusion. In contrast, having distinct Jira projects ensures that project-specific metadata is well organized and relevant. On the other hand, the Cassandra Sidecar has its own dedicated Jira project, which avoids these issues entirely. - Yifan On Tue, Oct 1, 2024 at 7:27 AM Brandon Williams <dri...@gmail.com> wrote: > 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 <j...@rustyrazorblade.com> 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 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 all drivers or one for each driver? > > > > Jon > > > > On Tue, Oct 1, 2024 at 10:16 AM Brandon Williams <dri...@gmail.com> > wrote: > >> > >> 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 <dri...@gmail.com> > wrote: > >> > > >> > 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 <jmcken...@apache.org> > wrote: > >> > > > >> > > +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 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 part of the Cassandra JIRA project > would imply less management overhead but the sub-project would need to > conform to the same workflows. > >> > > > >> > > I would pick option 1 unless there is a strong reason and desire to > manage a separate Jira project. We can always split out the Java Driver > project if things don't work out. OTOH merging a Jira project is harder. > >> > > > >> > > Thanks, > >> > > > >> > > Dinesh > >> > > > >> > > On Thu, Apr 4, 2024 at 12:45 PM Abe Ratnofsky <a...@aber.io> wrote: > >> > > > >> > > 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 vote > threads: > >> > > https://lists.apache.org/thread/01pljcncyjyo467l5orh8nf9okrh7oxm > >> > > https://lists.apache.org/thread/opt630do09phh7hlt28odztxdv6g58dp > >> > > https://lists.apache.org/thread/crolkrhd4y6tt3k4hsy204xomshlcp4p > >> > > > >> > > But looks like upon acceptance that was changed: > >> > > https://lists.apache.org/thread/dhov01s8dvvh3882oxhkmmfv4tqdd68o > >> > > > >> > > > New issues will be tracked under the CASSANDRA project on > Apache’s JIRA <https://issues.apache.org/jira/projects/CASSANDRA> under > the component ‘Client/java-driver’. > >> > > > >> > > I'm in favor of using the same Jira as Cassandra proper. > Committership is project-wide, so having a standardized process (same > ticket flow, review rules, labels, etc. is beneficial). But multiple votes > happened based on the content of the CEP, so we should stick to what was > voted on and move to a separate Jira. > >> > > > >> > > -- > >> > > Abe > >> > > > >> > > >
