> Just a heads up - this comes across as passive aggressive sniping. I'm sure
> you didn't mean it as such
I think indirect criticism is a normal part of discourse, particularly in
public fora where it can be more polite and less disruptive than direct
criticism. Ironically, this snippet of yours seem (to me) to be more readily
ascribed your epithet; which is fine, of course, and pleasingly meta.
> very little has publically materialized on the project to this point that I
> know of
I think you are wrong, here. Firstly, you overlook recent work such as (but
not limited to): FQL, cassandra-diff, in-jvm dtests; also the steady drip of
dozens of critical bugs found, and the work to fix those bugs. It is perhaps
unfair to label "very little" work that has spanned several years and uncovered
perhaps the majority of serious correctness bugs.
Secondly, there is an important distinction to draw, between QA projects that
are in progress but not yet published, and an absence of such projects. We
might also note feature development endeavours that have been initiated, and
whether work aims to improve quality or expand functionality. I look forward
to seeing the balance of investments shift to match stated priorities in the
near future.
On 27/06/2020, 03:10, "Joshua McKenzie" <jmcken...@apache.org> wrote:
>
> I've seen a lot of talk from some quarters of a new approach to quality,
> but so far there have been few contributions from the same quarters
>
Just a heads up - this comes across as passive aggressive sniping. I'm sure
you didn't mean it as such but it does read that way (at least to me).
When it comes to quality, much like you said in another thread Benedict I
think we all need to be honest with ourselves. There's been a lot of talk
from *all* quarters but outside a lot of expression of intent across many
fronts (verbal, ML, JIRA, slack), very little has publically materialized
on the project to this point that I know of.
I cleared out assignees on 40_quality_testing tickets earlier this week
(overloading shepherds in this field was a mistake IMO - that's on me)
which has clarified for some contributors that they can take that work on.
There's still considerable uncertainty as to what the scope is for those
tickets and nobody really replied to Jordan pinging shepherds for
clarification a long while ago.
On Fri, Jun 26, 2020 at 8:44 PM Dinesh Joshi <djo...@apache.org> wrote:
> > On Jun 26, 2020, at 3:45 PM, David Capwell <dcapw...@gmail.com> wrote:
> >
> > the ability to test their impact. Even simple things become hard given
> the
> > fact only committers can run Jenkins tests, or you pay money to be able
> to
> > run the tests... If the intent is to make it easier for new people to
> > contribute to the project, shouldn't the focus be on fixing their pain
> > points such as testing?
>
> +1 on not branching and keeping focus on testing and fixing 4.0.
>
> I am sorry about the situation for non-committers. I tried reaching out to
> legal and infra in the past without a great response. If someone in the
> community has a way to reach out and get clarity on problems affecting our
> contributors, it would be great. Otherwise, I will try to bug them again.
>
> Dinesh
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: dev-h...@cassandra.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org
