Hi,
Strong +1 as well. It's a pretty critical dependency in the path of testing and
committing changes. Supporting integration points for alternative distributions
of Cassandra is something I think we should generally be supportive as it's
generally an opportunity to make things more modular an
Sounds like we have a general consensus from the project on being willing to
accept the donation, should the current rights owners be interested in said
donation.
> We've been working on this along with the python-driver (just haven't raised
> it yet).
Which they indicate they are. :)
I'll fol
I would also love to see CCM as an official side project. It is important
to the project and I personally use it regularly.
Jordan
On Thu, May 16, 2024 at 7:55 AM Josh McKenzie wrote:
> We do still have the issues of DSE-supporting code in it, as we do with
> the drivers. I doubt any of us str
> We do still have the issues of DSE-supporting code in it, as we do with the
> drivers. I doubt any of us strongly object to it: there's no trickery
> happening here on the user; but we should be aware of it and have a rough
> direction sketched out for when someone else comes along wanting to
+1 (my personal opinion)
How to deal with the DSE-supporting code is a separate discussion IMO
- - -- --- - -
Jacek Lewandowski
czw., 16 maj 2024 o 10:21 Berenguer Blasi
napisał(a):
> +1 ccm is super useful
> On 16/5/24 10:09, Mick Semb Wever wrote:
>
>
>
> On Wed, 15
+1 ccm is super useful
On 16/5/24 10:09, Mick Semb Wever wrote:
On Wed, 15 May 2024 at 16:24, Josh McKenzie wrote:
Right now ccm isn't formally a subproject of Cassandra or under
governance of the ASF. Given it's an integral components of our CI
as well as for local testing for m
On Wed, 15 May 2024 at 16:24, Josh McKenzie wrote:
> Right now ccm isn't formally a subproject of Cassandra or under governance
> of the ASF. Given it's an integral components of our CI as well as for
> local testing for many devs, and we now have more experience w/our muscle
> on IP clearance an
Yes please!
> On May 15, 2024, at 2:23 PM, Bret McGuire wrote:
>
>Very much agreed Paulo; I was musing on the idea of adding Docker support
> to ccm recently as well. We'd want to preserve the current ability to work
> with releases (and Github branches) but I very much like the idea of a
Very much agreed Paulo; I was musing on the idea of adding Docker
support to ccm recently as well. We'd want to preserve the current ability
to work with releases (and Github branches) but I very much like the idea
of adding Docker support as a new feature.
On Wed, May 15, 2024 at 3:56 PM Paul
As much as I'd like to remove the dependency on ccm I think we'll stick
with it for a bit, so +1 on moving under the project umbrella.
In the long term it would be nice to modernize integration test suites to
use containers instead of processes for more flexibility and fewer
dependencies for local
Strong supporter for bringing ccm into the project as well. ccm is necessary
test infrastructure for multiple subprojects, and Cassandra committers should
be able to make the changes to ccm that are necessary for their patches.
There's also the security angle: we should work to consolidate our d
Speaking only for myself I _love_ this idea. The various drivers use
ccm extensively in their integration test suites so having this tool
in-house and actively looked after would be very beneficial for our work.
- Bret -
On Wed, May 15, 2024 at 9:23 AM Josh McKenzie wrote:
> Right now cc
Right now ccm isn't formally a subproject of Cassandra or under governance of
the ASF. Given it's an integral components of our CI as well as for local
testing for many devs, and we now have more experience w/our muscle on IP
clearance and ingesting / absorbing subprojects where we can't track d
13 matches
Mail list logo
