Could use some love, but not too bad.
On Fri, May 2, 2025 at 3:44 PM Patrick McFadin wrote:
> Lazily. Yes, bring it on over. But... how do the docs look? *runs away
>
> On Fri, May 2, 2025 at 12:39 PM Jon Haddad
> wrote:
>
>> Since we only need lazy consensus here - it sounds like i can go ahe
Lazily. Yes, bring it on over. But... how do the docs look? *runs away
On Fri, May 2, 2025 at 12:39 PM Jon Haddad wrote:
> Since we only need lazy consensus here - it sounds like i can go ahead and
> rename the repo to cassandra-easy-stress and transfer it over to Apache.
>
> On Thu, May 1, 2025
Since we only need lazy consensus here - it sounds like i can go ahead and
rename the repo to cassandra-easy-stress and transfer it over to Apache.
On Thu, May 1, 2025 at 1:37 PM Aaron wrote:
> +1
>
> On Thu, May 1, 2025 at 4:27 PM Dave Herrington
> wrote:
>
>> +1 (nb)
>>
>> -Dave
>>
>> On Wed,
+1 to docker. It’s a relatively universal dependency at this point, allows
for more repeatable builds, and doesn’t require installing software in the
build. It’s not any more heavyweight that go or python and has less
environment nuances. It lets us pick what python (or go) we use among many
other
On Fri, May 2, 2025 at 6:46 AM Mick Semb Wever wrote:
> But layering in the ability to do it with docker is opposed to requiring
> the use of docker. i.e. I don't think we should make docker mandatory
> inside `ant check`.
>
I think if you don't have docker it could be reasonable not to build t
“ I can only hope they understand and appreciate this *is* their work
being carried forward, and our legitimate reasons for the golang to python
rewrite (i.e. there's nothing against golang in the community). “
+1
Also, I would love to explore Maxim’s suggestion more. Option 1 still leads
to peo
When approaching the code for the first time, I think option 2 will be
the most consistent and have less friction since it won't be a
one-off. +1 from me.
Kind Regards,
Brandon
On Fri, May 2, 2025 at 5:47 AM Mick Semb Wever wrote:
>
>
>
> This can be done now using the following command (inste
This can be done now using the following command (instead of `ant check`):
.build/docker/check-code.sh
See readme under `.build/`
But layering in the ability to do it with docker is opposed to requiring
the use of docker. i.e. I don't think we should make docker mandatory
inside `ant check`.
