I would be sad to see us drop this just because it's a hard discussion with
a few different opinions. My apologies if this discussion is making folks
feel excluded.
Whilst I don't have a problem with a strict approach and it does improve
user clarity. I can understand how it might feel exclusionar
+1
> On Jun 30, 2021, at 4:38 PM, Brandon Williams wrote:
>
> Hello,
>
> Since our project governance requires two committers, which in some
> circumstances may mean two committers need to review, I'd like to add
> another state to our jira such that finding tickets that need a second
> review
>
> And I'm thinking of anyone that has to update this list and reason through
> all of the complex rulesets of why or why not, It's really not fair to
> them.
My proposal is that we completely drop the Cassandra Cloud Offereing
> section.
> Given that criteria, Professional Support and Education
+1 sounds good. I recall seeing the conversation in #cassandra-dev --
weren't you also going to add a tag so it's easy to pick the tickets that
need a second reviewer? Cheers!
Appreciate the discussion, all.
As the person who has primarily been aggregating info for this page, my
approach has been to consider what would be most useful to an end user who
wants to use / extend Cassandra -- and to be permissive about what would be
included to keep things simple (as we don't
Hello,
Since our project governance requires two committers, which in some
circumstances may mean two committers need to review, I'd like to add
another state to our jira such that finding tickets that need a second
reviewer is possible, since it is not currently.
On slack, Paulo Motta suggested
>
> My proposal is that we completely drop the Cassandra Cloud Offereing
> section.
+1
On Wed, Jun 30, 2021 at 12:34 PM Patrick McFadin wrote:
> This is a very interesting thread and has had me thinking quite a bit.
> Having to reason through who belongs on a list or not just seems very
> pol
Congrats to everyone that worked on this iteration. If you haven't looked
at the CHANGES.txt there were some great catches in RC1. Just like it
should happen!
On Wed, Jun 30, 2021 at 12:29 PM Mick Semb Wever wrote:
>
> The Cassandra team is pleased to announce the release of Apache Cassandra
> v
The Cassandra team is pleased to announce the release of Apache Cassandra
version 4.0-rc2.
Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.
http://cassandra.apache.org/
Downloads of source a
Looks like we all agree on option 1. I have submitted a patch to the trunk
branch. It unifies the duration unit and defaults to micros. As a result,
all timers will start to record time values in micros instead of nanos.
Please let me know if there is any concern with the change.
- Yifan
On Fri,
>
> The vote will be open for 72 hours (longer if needed). Everyone
> who has
> tested the build is invited to vote. Votes by PMC members are
> considered
> binding. A vote passes if there are at least three binding +1s
> and no
> >> -1's.
>
Vote passes wi
This is a very interesting thread and has had me thinking quite a bit.
Having to reason through who belongs on a list or not just seems very
polarizing to me and given the length of this thread, I think that's
playing out. This kind of energy is just not good for the larger community.
And I'm think
I disagree that disclaimers dissolve many duties, responsibilities or implied
communicative acts.
Most people recognise disclaimers as a means of abdicating responsibility for
the consequences of utilising an endorsement or other facility, not as a
communicative act indicating a lack of actual
13 matches
Mail list logo
