Hi everyone,
Thanks to hard work by Mick every push to the cassandra-website *src/*
directory in master is now automatically deployed to
https://cassandra.staged.apache.org/. The automation is carried out by a
Jenkins job at https://ci-cassandra.apache.org/job/cassandra-website/. This
is really us
As I mentioned, I really have nothing against asciidoc. In fact, I think
it's
great.
Let's just say that I think rst/sphinx is also pretty capable, and that I
consider
your characterization of the syntax difference (one "awful", the other "a
dream") a tad over-the-top. I do agree on the point on d
I agree with Benedict. We have a lot of organizational things going on
right now, perhaps we just mark it as deprecated in the docs and reference
alternatives in the readme? Then we can put this on a roadmap to revisit
post 4.0.
On Fri, May 1, 2020 at 7:50 AM Benedict Elliott Smith
wrote:
> I v
I vote to nuke it post-4.0, when we have time to put together a working group
to discuss its replacement.
On 30/04/2020, 19:21, "Mick Semb Wever" wrote:
The C* codebase contains the cassandra-stress tool that is seeing less
maintenance and is getting replaced in popularity by other too
The C* codebase contains the cassandra-stress tool that is seeing less
maintenance and is getting replaced in popularity by other tools in
our community. This raises the question of whether cassandra-stress
still belongs in-tree, and even in the apache project at all, as we
approach 4.0
A) Should
Updated CEP-2:
Without involving advanced automation that could involve resources specific to
Cloud Service provider, the following could be added.
- Automatic backup and restore operations- Role-based access control (RBAC)
Automated Security Management- Automated Monitoring Through Prometheus
Hi all,
going with asciidoc is a great choice and I can only agree with all
Jon said. It is rich in its capabilities as well as in support and
integration into whatever (browser plugins, IDEA plugins, build
plugins ...).
Even though it is not related to technicalities, I find it important
to high
I've got a bit of experience here using all three systems we're discussing
here.
* rst & sphinx: I've handled most of the doc reviews for Cassandra, written
quite a bit of them as well, and I authored most of the documentation for
cqlengine [1]
* markdown: all over the place, let's be honest, it's
I do worry Markdown might not be a great choice.
It's definitively most well know by a large margin, and that's a good, but
it's also a bit limited (even with common extensions). It's perfect for
comments, README or even somewhat informal docs, but we're talking the
fairly
large (and meant to grow
The vote passed with 4 +1 votes (including mine) and 0 -1s.
On Thu, Apr 30, 2020 at 10:51 AM Marcus Eriksson wrote:
> +1
>
>
> On 29 April 2020 at 17:08:57, David Capwell (dcapw...@apple.com.invalid)
> wrote:
> > +1.
> > Checked integration with Cassandra and upgrade
> >
> > Sent from my iPhone
+1
On 29 April 2020 at 17:08:57, David Capwell (dcapw...@apple.com.invalid) wrote:
> +1.
> Checked integration with Cassandra and upgrade
>
> Sent from my iPhone
>
> > On Apr 29, 2020, at 4:01 AM, Mick Semb Wever wrote:
> >
> >
> >>
> >> Proposing the test build of in-jvm dtest API 0.0.2 fo
11 matches
Mail list logo
