I’ve added a “LHF” quick filter to the board which filters on this. You may
have to click “Show More” to make it visible.
Jordan
On Tue, Apr 7, 2020 at 6:09 PM wrote:
> Hi Manish,
> You can check those tickets which have Complexity: Low Hanging Fruit
>
> Ekaterina
>
> Sent from my iPhone
>
> >
+1 (nb) to the change and +1 (nb) to updating the docs to reflect this.
Jordan
On Wed, Apr 8, 2020 at 11:30 AM wrote:
> +1
>
> > El 8 abr 2020, a las 19:05, e.dimitr...@gmail.com escribió:
> >
> > +1
> >
> > Sent from my iPhone
> >
> >> On 8 Apr 2020, at 13:50, Joshua McKenzie wrote:
> >>
> >
+1
> El 8 abr 2020, a las 19:05, e.dimitr...@gmail.com escribió:
>
> +1
>
> Sent from my iPhone
>
>> On 8 Apr 2020, at 13:50, Joshua McKenzie wrote:
>>
>> +1
>>
On Wed, Apr 8, 2020 at 12:26 PM Sam Tunnicliffe wrote:
>>>
>>> +1
>>>
> On 8 Apr 2020, at 15:08, Mick Semb Wever wro
+1
Sent from my iPhone
> On 8 Apr 2020, at 13:50, Joshua McKenzie wrote:
>
> +1
>
>> On Wed, Apr 8, 2020 at 12:26 PM Sam Tunnicliffe wrote:
>>
>> +1
>>
On 8 Apr 2020, at 15:08, Mick Semb Wever wrote:
>>>
>>> Can we agree on keeping such test changes out of CHANGES.txt ?
>>>
>>> We
On CASSANDRA-15379, I think we would’ve discovered this issue during 4.0
testing and would have needed this bug fix anyway. We just caught it early
because you went ahead and tested the feature ;)
Dinesh
> On Mar 31, 2020, at 3:27 PM, Joseph Lynch wrote:
>
> On Tue, Mar 31, 2020 at 1:27 PM J
+1
On Wed, Apr 8, 2020 at 12:26 PM Sam Tunnicliffe wrote:
> +1
>
> > On 8 Apr 2020, at 15:08, Mick Semb Wever wrote:
> >
> > Can we agree on keeping such test changes out of CHANGES.txt ?
> >
> > We already don't put entries into CHANGES.txt if it is not a change
> > from any previous release.
+1
On Wed, Apr 8, 2020, 10:06 AM Dinesh Joshi wrote:
> Could we please update the developer docs to reflect this?
>
> http://cassandra.apache.org/doc/latest/development/index.html
>
> Dinesh
>
> > On Apr 8, 2020, at 7:08 AM, Mick Semb Wever wrote:
> >
> > Can we agree on keeping such test chang
Could we please update the developer docs to reflect this?
http://cassandra.apache.org/doc/latest/development/index.html
Dinesh
> On Apr 8, 2020, at 7:08 AM, Mick Semb Wever wrote:
>
> Can we agree on keeping such test changes out of CHANGES.txt ?
>
> We already don't put entries into CHANGES
+1
> On 8 Apr 2020, at 15:08, Mick Semb Wever wrote:
>
> Can we agree on keeping such test changes out of CHANGES.txt ?
>
> We already don't put entries into CHANGES.txt if it is not a change
> from any previous release.
>
> There was some discussion before¹ about this, and the problem that
>
Dear Cassandra community,
Recently I have reported
[CASSANDRA-15623](https://issues.apache.org/jira/browse/CASSANDRA-15623)
and submitted a patch for it, please see the ticket for more details.
The patch has been reviewed and approved for merging into trunk.
However, now there is a need to de
+1
From: Jasonstack Zhao Yang
Sent: Wednesday, April 8, 2020 9:04:51 AM
To: dev@cassandra.apache.org
Subject: Re: Keeping test-only changes out of CHANGES.txt
+1
On Thu, Apr 9, 2020, 00:04 Aleksey Yeshchenko
wrote:
> +1
>
> > On 8 Apr 2020, at 15:08, Mick Sem
+1
On Thu, Apr 9, 2020, 00:04 Aleksey Yeshchenko
wrote:
> +1
>
> > On 8 Apr 2020, at 15:08, Mick Semb Wever wrote:
> >
> > Can we agree on keeping such test changes out of CHANGES.txt ?
> >
> > We already don't put entries into CHANGES.txt if it is not a change
> > from any previous release.
>
+1
> On 8 Apr 2020, at 15:08, Mick Semb Wever wrote:
>
> Can we agree on keeping such test changes out of CHANGES.txt ?
>
> We already don't put entries into CHANGES.txt if it is not a change
> from any previous release.
>
> There was some discussion before¹ about this, and the problem that
>
+1
On 08/04/2020, 16:53, "Mick Semb Wever" wrote:
Can we agree on keeping such test changes out of CHANGES.txt ?
We already don't put entries into CHANGES.txt if it is not a change
from any previous release.
There was some discussion before¹ about this, and the problem
Can we agree on keeping such test changes out of CHANGES.txt ?
We already don't put entries into CHANGES.txt if it is not a change
from any previous release.
There was some discussion before¹ about this, and the problem that
being selective meant what ended up there being arbitrary. I think
this
15 matches
Mail list logo
