everyone,
> >>>>
> >>>> Now that many teams have begun testing and validating Apache Cassandra
> >>>> 4.0, it’s useful to think about what “progress” looks like. While
> >> metrics
> >>>> alone may not tell us what “done” me
, and
>>>> consequent:
>>>>
>>>> – Actionable: We know what to do based on them – where to invest, what
>> to
>>>> fix, what’s fine, etc.
>>>> – Visible: Everyone who has a stake in a metric has full visibility into
>>>> it and part
against build abc predict an x%
> >> reduction in 99%ile read latency for this workload in prod".
> >> – Consequent: We take actions based on them (e.g., not shipping if tests
> >> are failing).
> >>
> >> Here are some notes in Confluence toward metrics
ns based on them (e.g., not shipping if tests
>> are failing).
>>
>> Here are some notes in Confluence toward metrics that may be useful to
>> track beginning in this phase of the development + release cycle. I’m
>> interested in your thoughts on these. They’re also copi
. I’m
>> interested in your thoughts on these. They’re also copied inline for easier
>> reading in your mail client.
>>
>> Link:
>> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=93324430
>>
>> Cheers,
>>
>> – Scott
>>
>
le. I’m
> interested in your thoughts on these. They’re also copied inline for easier
> reading in your mail client.
>
> Link:
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=93324430
>
> Cheers,
>
> – Scott
>
> ––
>
> Measuring Release Qu
lient.
Link: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=93324430
Cheers,
– Scott
––––––
Measuring Release Quality:
[ This document is a draft + sketch of ideas. It is located in the "discussion"
section of this wiki to indicate that it is an active draft –
