s consensus and last Friday committed it,
> along with the documentation update from Eduard.
>
> https://github.com/apache/cassandra/commit/141ea26733e7e8fe022bc78f7fd68225013e8d14
>
> So this is also reflected in the CHANGES.t
ub.com/apache/cassandra/commit/141ea26733e7e8fe022bc78f7fd68225013e8d14
So this is also reflected in the CHANGES.txt found in 4.0-alpha4
regards,
Mick
-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional co
out as well.
> > Anyone object to eliding documentation changes from CHANGES.txt?
> >
>
> +1 It will just get too noisy otherwise.
>
>
> In a conversation with Mick we discussed keeping doc changes out as well.
> Anyone object to eliding documentation changes from CHANGES.txt?
>
+1 It will just get too noisy otherwise.
> > > updated docs in https://github.com/apache/cassandra/pull/528
> > >
Thanks Eduard and Jon.
Committed in
https://github.com/apache/cassandra/commit/141ea26733e7e8fe022bc78f7fd68225013e8d14
-
To unsubscribe, e-mail: dev-uns
wrote:
>>
>> In a conversation with Mick we discussed keeping doc changes out as well.
>> Anyone object to eliding documentation changes from CHANGES.txt?
>>
>>
>>
>>
>>
>>
>> On Thu, Apr 9, 2020 at 1:07 AM Benjamin Lerer
>> wro
+1 for keeping doc changes out. Definitely no good reason for keeping them.
On Fri, Apr 10, 2020 at 1:39 PM Jon Haddad wrote:
>
> In a conversation with Mick we discussed keeping doc changes out as well.
> Anyone object to eliding documentation changes from CHANGES.txt?
>
>
&
In a conversation with Mick we discussed keeping doc changes out as well.
Anyone object to eliding documentation changes from CHANGES.txt?
On Thu, Apr 9, 2020 at 1:07 AM Benjamin Lerer
wrote:
> +1
>
>
>
> On Thu, Apr 9, 2020 at 9:28 AM Eduard Tudenhoefner <
> > > > 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
> > >>>> 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
gt; 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 wr
gt;
>>> +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
+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 a
+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 n
t; 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 select
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
+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¹ abo
+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
+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 n
+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¹ abo
+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¹ abou
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
Thanks your responses! Seems like all of you prefer to have both trivial
and non-trivial updates in CHANGES.txt. I'm going to keep that in mind,
but will continue to omit them for documentation edits.
On 18.07.2017 23:49, kurt greaves wrote:
> I agree that all patches should be
I agree that all patches should be added to changes.txt, just to rule out
any ambiguities. When people look at Changes.txt it's usually to find
something specific, not to browse the list of changes. Anything significant
should make it into news.txt, which is more appropriate for users.
change
I also think all issues should be kept in CHANGES.txt, it very useful either to
find what changed or to track some obscure bugs months after the release.
Sometime when developing plugins for Cassandra you find solutions/resolution
there.
Maybe if you want to reduce the list you could provide a
On Tue, Jul 18, 2017 at 8:10 AM, Stefan Podkowinski wrote:
> Has there been any consensus in the past about what goes into
> CHANGES.txt and what not? My naive assumption was that the intended
> audience for the file are users who want to know about changes between
> new releases. Ha
Has there been any consensus in the past about what goes into
CHANGES.txt and what not? My naive assumption was that the intended
audience for the file are users who want to know about changes between
new releases. Having that in mind, I skipped changes.txt once in a while
for updates that have no
Paulo pinged me on irc about getting CASSANDRA-12905 in for 3.10, so
that has been marked as release critical for 3.10 in JIRA.
--
Kind regards,
Michael
On 12/05/2016 01:26 PM, Michael Shuler wrote:
> I have again removed the 3.11 version from JIRA and corrected
> CHANGES.txt fo
I have again removed the 3.11 version from JIRA and corrected
CHANGES.txt for 3.10.
I'll run through the test results on the cassandra-3.11 branch and see
where we are at for a possible 3.10 release vote #5. There appear to be
no open 3.10 JIRA tickets at this time.
--
Kind regards,
Michae
Sam and I fixed up CHANGES.txt and fix versions in JIRA that had 3.11.
Since 3.10 has not been released yet,and the cassandra-3.11 branch was
created from the 3.10-tentative tag for fixed on top of 3.10, the
cassandra-3.11 branch will be used for the 3.10 release, as well as for
fixed bugs on top
I don't find mention of max_mutation_size_in_kb in CHANGES.txt, but I do
see it mentioned for 3.0.0 in NEWS.txt. It doesn't have (DataStax) doc
either.
It looks like it was added on 8/19/2015: "patch by Aleksey Yeschenko;
reviewed by Benedict Elliott Smith for CASSANDRA-6230"
Added. Thanks for catching that!
On Thu, Sep 15, 2011 at 11:37 PM, aaron morton wrote:
> It's in NEWS should it also be in CHANGES?
>
> https://issues.apache.org/jira/browse/CASSANDRA-2449
>
> Cheers
>
>
> -
> Aaron Morton
> Freelance Cassandra Developer
> @aaronmorton
> http://w
It's in NEWS should it also be in CHANGES?
https://issues.apache.org/jira/browse/CASSANDRA-2449
Cheers
-
Aaron Morton
Freelance Cassandra Developer
@aaronmorton
http://www.thelastpickle.com
when cassandra 0.6 release official ?
2010/4/9
> Author: jbellis
> Date: Fri Apr 9 14:34:44 2010
> New Revision: 932433
>
> URL: http://svn.apache.org/viewvc?rev=932433&view=rev
> Log:
> update CHANGES
>
> Modified:
> cassandra/branches/cassandra-0.6/C
34 matches
Mail list logo
