Proposing the test build of Cassandra 3.11.16 for release.
sha1: f86929eae086aa108cf58ee0164c3d12a59ad4af
Git: https://github.com/apache/cassandra/tree/3.11.16-tentative
Maven Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1305/org/apache/cassandra/cassandra-all/
The test build of Cassandra 3.11.16 is available.
sha1: f86929eae086aa108cf58ee0164c3d12a59ad4af
Git: https://github.com/apache/cassandra/tree/3.11.16-tentative
Maven Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1305/org/apache/cassandra/cassandra-all/3.11.16/
I think it would be good for the project to have an official PyPI distribution,
and the signal from users (40K downloads per month) is a clear indication that
this is useful. Timely releases would help us get future improvements to cqlsh
out faster, and moving this to an official distribution wo
HI Dinesh,
You are correct that the scope of this CEP is practical, narrow and limited
to having an official distribution of CQLSH on the official Python package
repository. Cassandra end-users, who use the CQLSH command line, would
benefit in several direct ways:
- A timely distribution of ne
Brad,
Thanks for starting this discussion. My understanding is that we're
simply adding pip support for cqlsh and Apache Cassandra project will
officially publish a cqlsh pip package. This is a good goal but other
than having an official pip package, what is it that we're gaining?
Please don't int
As per the CEP process guidelines, I'm starting a formal DISCUSS thread to
resume the conversation started here[1].
The developers who maintain the Python CQLSH client on the official Python
PYPI repository would like to integrate and donate their open source work
to the Apache Cassandra project s
On Wed, Aug 9, 2023 at 8:48 AM Ekaterina Dimitrova
wrote:
>
> Just thinking it might be easier to do the releases all together, from
> operational perspective
I personally think, if anything, it's more overhead having multiple
releases in flight simultaneously.
I agree, we have enough for a release of 3.0 and 3.11 and if there are
users expecting it, I don’t see a reason why not to cut releases. Shall we
do it together with 5.0 alpha? There was a mention that one might be cut
soon, as far as I recall. Just thinking it might be easier to do the
releases al
On Wed, Aug 9, 2023 at 3:58 AM Miklosovic, Stefan
wrote:
> There is a user on Slack asking for a release of 3.11.16 because of 16555.
If people are showing interest, I think it's time.
> If we release right now, we might potentially do one more release before 5.0
> is GA.
I think 5.0 is still
Hi,
with 5.0 getting closer, when do we plan to release the last releases of 3.0.x
and 3.11.x?
There is a user on Slack asking for a release of 3.11.16 because of 16555.
If we release right now, we might potentially do one more release before 5.0 is
GA.
Do you think it makes sense to releas
10 matches
Mail list logo
