Re: Welcome Stefan Miklosovic as Cassandra committer

[Berenguer Blasi]

Congrats Stefan!

On 3/5/21 22:24, Yifan Cai wrote:
> Congrats!
>
> On Mon, May 3, 2021 at 1:23 PM Paulo Motta  wrote:
>
>> Congrats, Stefan! Happy to see you onboard! :)
>>
>> Em seg., 3 de mai. de 2021 às 17:17, Ben Bromhead 
>> escreveu:
>>
>>> Congrats mate!
>>>
>>> On Tue, May 4, 2021 at 4:20 AM Scott Andreas 
>> wrote:
 Congratulations, Štefan!

 
 From: David Capwell 
 Sent: Monday, May 3, 2021 10:53 AM
 To: dev@cassandra.apache.org
 Subject: Re: Welcome Stefan Miklosovic as Cassandra committer

 Congrats!

> On May 3, 2021, at 9:47 AM, Ekaterina Dimitrova <
>> e.dimitr...@gmail.com
 wrote:
> Congrat Stefan! Well done!!
>
> On Mon, 3 May 2021 at 11:49, J. D. Jordan >>> wrote:
>> Well deserved!  Congrats Stefan.
>>
>>> On May 3, 2021, at 10:46 AM, Sumanth Pasupuleti <
>> sumanth.pasupuleti...@gmail.com> wrote:
>>> Congratulations Stefan!!
>>>
 On Mon, May 3, 2021 at 8:41 AM Brandon Williams > wrote:
 Congratulations, Stefan!

> On Mon, May 3, 2021 at 10:38 AM Benjamin Lerer <
>> b.le...@gmail.com>
>> wrote:
> The PMC's members are pleased to announce that Stefan Miklosovic
>>> has
> accepted the invitation to become committer last Wednesday.
>
> Thanks a lot, Stefan,  for all your contributions!
>
> Congratulations and welcome
>
> The Apache Cassandra PMC members

>>> -
 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
>>
>>

 -
 To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
 For additional commands, e-mail: dev-h...@cassandra.apache.org

 --
>>> Ben Bromhead
>>>
>>> Instaclustr | www.instaclustr.com | @instaclustr
>>>  | +64 27 383 8975
>>>

-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org

Re: Welcome Stefan Miklosovic as Cassandra committer

[Yifan Cai]

Congrats!

On Mon, May 3, 2021 at 1:23 PM Paulo Motta  wrote:

> Congrats, Stefan! Happy to see you onboard! :)
>
> Em seg., 3 de mai. de 2021 às 17:17, Ben Bromhead 
> escreveu:
>
> > Congrats mate!
> >
> > On Tue, May 4, 2021 at 4:20 AM Scott Andreas 
> wrote:
> >
> > > Congratulations, Štefan!
> > >
> > > 
> > > From: David Capwell 
> > > Sent: Monday, May 3, 2021 10:53 AM
> > > To: dev@cassandra.apache.org
> > > Subject: Re: Welcome Stefan Miklosovic as Cassandra committer
> > >
> > > Congrats!
> > >
> > > > On May 3, 2021, at 9:47 AM, Ekaterina Dimitrova <
> e.dimitr...@gmail.com
> > >
> > > wrote:
> > > >
> > > > Congrat Stefan! Well done!!
> > > >
> > > > On Mon, 3 May 2021 at 11:49, J. D. Jordan  >
> > > wrote:
> > > >
> > > >> Well deserved!  Congrats Stefan.
> > > >>
> > > >>> On May 3, 2021, at 10:46 AM, Sumanth Pasupuleti <
> > > >> sumanth.pasupuleti...@gmail.com> wrote:
> > > >>>
> > > >>> Congratulations Stefan!!
> > > >>>
> > >  On Mon, May 3, 2021 at 8:41 AM Brandon Williams  >
> > > >> wrote:
> > > 
> > >  Congratulations, Stefan!
> > > 
> > > > On Mon, May 3, 2021 at 10:38 AM Benjamin Lerer <
> b.le...@gmail.com>
> > > >> wrote:
> > > >
> > > > The PMC's members are pleased to announce that Stefan Miklosovic
> > has
> > > > accepted the invitation to become committer last Wednesday.
> > > >
> > > > Thanks a lot, Stefan,  for all your contributions!
> > > >
> > > > Congratulations and welcome
> > > >
> > > > The Apache Cassandra PMC members
> > > 
> > > 
> > -
> > >  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
> > > >>
> > > >>
> > >
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> > > For additional commands, e-mail: dev-h...@cassandra.apache.org
> > >
> > > --
> >
> > Ben Bromhead
> >
> > Instaclustr | www.instaclustr.com | @instaclustr
> >  | +64 27 383 8975
> >
>

Re: Welcome Stefan Miklosovic as Cassandra committer

[Paulo Motta]

Congrats, Stefan! Happy to see you onboard! :)

Em seg., 3 de mai. de 2021 às 17:17, Ben Bromhead 
escreveu:

> Congrats mate!
>
> On Tue, May 4, 2021 at 4:20 AM Scott Andreas  wrote:
>
> > Congratulations, Štefan!
> >
> > 
> > From: David Capwell 
> > Sent: Monday, May 3, 2021 10:53 AM
> > To: dev@cassandra.apache.org
> > Subject: Re: Welcome Stefan Miklosovic as Cassandra committer
> >
> > Congrats!
> >
> > > On May 3, 2021, at 9:47 AM, Ekaterina Dimitrova  >
> > wrote:
> > >
> > > Congrat Stefan! Well done!!
> > >
> > > On Mon, 3 May 2021 at 11:49, J. D. Jordan 
> > wrote:
> > >
> > >> Well deserved!  Congrats Stefan.
> > >>
> > >>> On May 3, 2021, at 10:46 AM, Sumanth Pasupuleti <
> > >> sumanth.pasupuleti...@gmail.com> wrote:
> > >>>
> > >>> Congratulations Stefan!!
> > >>>
> >  On Mon, May 3, 2021 at 8:41 AM Brandon Williams 
> > >> wrote:
> > 
> >  Congratulations, Stefan!
> > 
> > > On Mon, May 3, 2021 at 10:38 AM Benjamin Lerer 
> > >> wrote:
> > >
> > > The PMC's members are pleased to announce that Stefan Miklosovic
> has
> > > accepted the invitation to become committer last Wednesday.
> > >
> > > Thanks a lot, Stefan,  for all your contributions!
> > >
> > > Congratulations and welcome
> > >
> > > The Apache Cassandra PMC members
> > 
> > 
> -
> >  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
> > >>
> > >>
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> > For additional commands, e-mail: dev-h...@cassandra.apache.org
> >
> > --
>
> Ben Bromhead
>
> Instaclustr | www.instaclustr.com | @instaclustr
>  | +64 27 383 8975
>

Re: Welcome Stefan Miklosovic as Cassandra committer

[Ben Bromhead]

Congrats mate!

On Tue, May 4, 2021 at 4:20 AM Scott Andreas  wrote:

> Congratulations, Štefan!
>
> 
> From: David Capwell 
> Sent: Monday, May 3, 2021 10:53 AM
> To: dev@cassandra.apache.org
> Subject: Re: Welcome Stefan Miklosovic as Cassandra committer
>
> Congrats!
>
> > On May 3, 2021, at 9:47 AM, Ekaterina Dimitrova 
> wrote:
> >
> > Congrat Stefan! Well done!!
> >
> > On Mon, 3 May 2021 at 11:49, J. D. Jordan 
> wrote:
> >
> >> Well deserved!  Congrats Stefan.
> >>
> >>> On May 3, 2021, at 10:46 AM, Sumanth Pasupuleti <
> >> sumanth.pasupuleti...@gmail.com> wrote:
> >>>
> >>> Congratulations Stefan!!
> >>>
>  On Mon, May 3, 2021 at 8:41 AM Brandon Williams 
> >> wrote:
> 
>  Congratulations, Stefan!
> 
> > On Mon, May 3, 2021 at 10:38 AM Benjamin Lerer 
> >> wrote:
> >
> > The PMC's members are pleased to announce that Stefan Miklosovic has
> > accepted the invitation to become committer last Wednesday.
> >
> > Thanks a lot, Stefan,  for all your contributions!
> >
> > Congratulations and welcome
> >
> > The Apache Cassandra PMC members
> 
>  -
>  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
> >>
> >>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: dev-h...@cassandra.apache.org
>
> --

Ben Bromhead

Instaclustr | www.instaclustr.com | @instaclustr
 | +64 27 383 8975

Re: Welcome Stefan Miklosovic as Cassandra committer

[Scott Andreas]

Congratulations, Štefan!


From: David Capwell 
Sent: Monday, May 3, 2021 10:53 AM
To: dev@cassandra.apache.org
Subject: Re: Welcome Stefan Miklosovic as Cassandra committer

Congrats!

> On May 3, 2021, at 9:47 AM, Ekaterina Dimitrova  wrote:
>
> Congrat Stefan! Well done!!
>
> On Mon, 3 May 2021 at 11:49, J. D. Jordan  wrote:
>
>> Well deserved!  Congrats Stefan.
>>
>>> On May 3, 2021, at 10:46 AM, Sumanth Pasupuleti <
>> sumanth.pasupuleti...@gmail.com> wrote:
>>>
>>> Congratulations Stefan!!
>>>
 On Mon, May 3, 2021 at 8:41 AM Brandon Williams 
>> wrote:

 Congratulations, Stefan!

> On Mon, May 3, 2021 at 10:38 AM Benjamin Lerer 
>> wrote:
>
> The PMC's members are pleased to announce that Stefan Miklosovic has
> accepted the invitation to become committer last Wednesday.
>
> Thanks a lot, Stefan,  for all your contributions!
>
> Congratulations and welcome
>
> The Apache Cassandra PMC members

 -
 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
>>
>>


-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org

How to make Cassandra flush CommitLog files more frequently?

[Bingqin Zhou]

Hi,

We're working with the CDC feature to develop an agent to stream changes in
Cassandra DB into Kafka. However, the CDC feature doesn't work well for us
so far because CommitLog files are rarely flushed into cdc_raw directory,
and the frequency can be as low as a few months.

Is there any suggested and feasible way to increase the frequency for
Cassandra to flush CommitLog files please?

We're thinking about decreasing *commitlog_segment_size_in_mb* from 32 to
16, and decreasing *commitlog_total_space_in_mb* from 8192 to 160. Does
this sound like a reasonable approach? Is there any concern or anything we
need to be warned about trying this please?

Thank you!

Bingqin Zhou

Re: Welcome Stefan Miklosovic as Cassandra committer

[David Capwell]

Congrats!

> On May 3, 2021, at 9:47 AM, Ekaterina Dimitrova  wrote:
> 
> Congrat Stefan! Well done!!
> 
> On Mon, 3 May 2021 at 11:49, J. D. Jordan  wrote:
> 
>> Well deserved!  Congrats Stefan.
>> 
>>> On May 3, 2021, at 10:46 AM, Sumanth Pasupuleti <
>> sumanth.pasupuleti...@gmail.com> wrote:
>>> 
>>> Congratulations Stefan!!
>>> 
 On Mon, May 3, 2021 at 8:41 AM Brandon Williams 
>> wrote:
 
 Congratulations, Stefan!
 
> On Mon, May 3, 2021 at 10:38 AM Benjamin Lerer 
>> wrote:
> 
> The PMC's members are pleased to announce that Stefan Miklosovic has
> accepted the invitation to become committer last Wednesday.
> 
> Thanks a lot, Stefan,  for all your contributions!
> 
> Congratulations and welcome
> 
> The Apache Cassandra PMC members
 
 -
 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
>> 
>> 


-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org

Re: Welcome Stefan Miklosovic as Cassandra committer

[Ekaterina Dimitrova]

Congrat Stefan! Well done!!

On Mon, 3 May 2021 at 11:49, J. D. Jordan  wrote:

> Well deserved!  Congrats Stefan.
>
> > On May 3, 2021, at 10:46 AM, Sumanth Pasupuleti <
> sumanth.pasupuleti...@gmail.com> wrote:
> >
> > Congratulations Stefan!!
> >
> >> On Mon, May 3, 2021 at 8:41 AM Brandon Williams 
> wrote:
> >>
> >> Congratulations, Stefan!
> >>
> >>> On Mon, May 3, 2021 at 10:38 AM Benjamin Lerer 
> wrote:
> >>>
> >>> The PMC's members are pleased to announce that Stefan Miklosovic has
> >>> accepted the invitation to become committer last Wednesday.
> >>>
> >>> Thanks a lot, Stefan,  for all your contributions!
> >>>
> >>> Congratulations and welcome
> >>>
> >>> The Apache Cassandra PMC members
> >>
> >> -
> >> 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
>
>

Re: Welcome Stefan Miklosovic as Cassandra committer

[J. D. Jordan]

Well deserved!  Congrats Stefan.

> On May 3, 2021, at 10:46 AM, Sumanth Pasupuleti 
>  wrote:
> 
> Congratulations Stefan!!
> 
>> On Mon, May 3, 2021 at 8:41 AM Brandon Williams  wrote:
>> 
>> Congratulations, Stefan!
>> 
>>> On Mon, May 3, 2021 at 10:38 AM Benjamin Lerer  wrote:
>>> 
>>> The PMC's members are pleased to announce that Stefan Miklosovic has
>>> accepted the invitation to become committer last Wednesday.
>>> 
>>> Thanks a lot, Stefan,  for all your contributions!
>>> 
>>> Congratulations and welcome
>>> 
>>> The Apache Cassandra PMC members
>> 
>> -
>> 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

Re: Welcome Stefan Miklosovic as Cassandra committer

[Sumanth Pasupuleti]

Congratulations Stefan!!

On Mon, May 3, 2021 at 8:41 AM Brandon Williams  wrote:

> Congratulations, Stefan!
>
> On Mon, May 3, 2021 at 10:38 AM Benjamin Lerer  wrote:
> >
> >  The PMC's members are pleased to announce that Stefan Miklosovic has
> > accepted the invitation to become committer last Wednesday.
> >
> > Thanks a lot, Stefan,  for all your contributions!
> >
> > Congratulations and welcome
> >
> > The Apache Cassandra PMC members
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: dev-h...@cassandra.apache.org
>
>

Re: Welcome Stefan Miklosovic as Cassandra committer

[Brandon Williams]

Congratulations, Stefan!

On Mon, May 3, 2021 at 10:38 AM Benjamin Lerer  wrote:
>
>  The PMC's members are pleased to announce that Stefan Miklosovic has
> accepted the invitation to become committer last Wednesday.
>
> Thanks a lot, Stefan,  for all your contributions!
>
> Congratulations and welcome
>
> The Apache Cassandra PMC members

-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org

Welcome Stefan Miklosovic as Cassandra committer

[Benjamin Lerer]

 The PMC's members are pleased to announce that Stefan Miklosovic has
accepted the invitation to become committer last Wednesday.

Thanks a lot, Stefan,  for all your contributions!

Congratulations and welcome

The Apache Cassandra PMC members

Re: [DISCUSS] Semantic versioning after 4.0

[Benedict Elliott Smith]

For a minor/major? I can imagine doing this for a patch version, but this is of 
much less importance to downstream users.

Do you have any examples of projects that do this for major/minor development 
branches, as you propose?

I'm just a bit confused about the proposition to decouple from releases, when 
the whole point of semver is that it's a public API that we honour around 
compatibility, so it is sort of intrinsically coupled to releases. It just 
sounds like a way to make our lives more complicated too, as it's less clear 
what releases are actually extant.


On 03/05/2021, 11:31, "Mick Semb Wever"  wrote:

> > Vendors are also free to support and provide hot-fixes and back ports 
on these unreleased versions, outside of the community's efforts or concerns
>
> This seems to me like we're endorsing the release of these versions by 
downstream maintainers? Even if we decide to modify this proposal and say "no, 
we don't endorse that," how do we prevent it?
>


We have to be explicit that semantic versioning != releases. That only
some version numbers get formal releases attached to them. And only
some of those releases get release branches to them. That is, we are
separating the concerns of versioning and releases for dev community
benefit.

I know some Apache projects don't do takeX re-votes on repeated
release attempts. Instead they fix the problem (that caused the vote
to fail), increment the version, and start a new vote on a new release
with a new version. These projects then have versions that are never
released, though this example is not to do with semver.

-
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

Re: [DISCUSS] Semantic versioning after 4.0

[Mick Semb Wever]

> > Vendors are also free to support and provide hot-fixes and back ports on 
> > these unreleased versions, outside of the community's efforts or concerns
>
> This seems to me like we're endorsing the release of these versions by 
> downstream maintainers? Even if we decide to modify this proposal and say 
> "no, we don't endorse that," how do we prevent it?
>


We have to be explicit that semantic versioning != releases. That only
some version numbers get formal releases attached to them. And only
some of those releases get release branches to them. That is, we are
separating the concerns of versioning and releases for dev community
benefit.

I know some Apache projects don't do takeX re-votes on repeated
release attempts. Instead they fix the problem (that caused the vote
to fail), increment the version, and start a new vote on a new release
with a new version. These projects then have versions that are never
released, though this example is not to do with semver.

-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org

Re: [DISCUSS] Semantic versioning after 4.0

[Benedict Elliott Smith]

> Vendors are also free to support and provide hot-fixes and back ports on 
> these unreleased versions, outside of the community's efforts or concerns

This seems to me like we're endorsing the release of these versions by 
downstream maintainers? Even if we decide to modify this proposal and say "no, 
we don't endorse that," how do we prevent it?

What's the benefit of this approach over using snapshot tags, if the goal is 
just making downstream maintainer's lives easier wrt merging a year's worth of 
work? 

On 03/05/2021, 10:09, "Mick Semb Wever"  wrote:

> Well the other problem I see is that this could create a lot of confusion 
for our users, if more versions start popping up (and/or versions are skipped). 
It's hard to row back from unwanted versions in the wild, and we may end up 
having to either support them or disappoint our users.


This is not made explicit to users. Not through announcements or
formal releases. This is strictly within dev.

Any bugs reported back upstream to the community in the dev cycle will
be fixed in trunk, that's the stated dev cycle and we don't deviate.

-
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

Re: [DISCUSS] Semantic versioning after 4.0

[Mick Semb Wever]

> Well the other problem I see is that this could create a lot of confusion for 
> our users, if more versions start popping up (and/or versions are skipped). 
> It's hard to row back from unwanted versions in the wild, and we may end up 
> having to either support them or disappoint our users.


This is not made explicit to users. Not through announcements or
formal releases. This is strictly within dev.

Any bugs reported back upstream to the community in the dev cycle will
be fixed in trunk, that's the stated dev cycle and we don't deviate.

-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org

Re: [DISCUSS] Semantic versioning after 4.0

[Benedict Elliott Smith]

Well the other problem I see is that this could create a lot of confusion for 
our users, if more versions start popping up (and/or versions are skipped). 
It's hard to row back from unwanted versions in the wild, and we may end up 
having to either support them or disappoint our users.

Do we have any examples of this approach being used elsewhere?

It just seems to me if the goal is to make more manageable downstream updates, 
a quarterly (or monthly) snapshot of latest might suffice, which can be done 
without potentially messing with our release cycle? Perhaps I'm missing 
something though.


On 03/05/2021, 09:44, "Mick Semb Wever"  wrote:

> Hmm, ok. I see some possible issues with this. You mention one 
possibility, i.e. that downstream may end up releasing these versions for us? 
Which potentially complicates our lives, whether we want it or not.
>
> Would this apply to only trunk, or to all existing major/minor releases?


Only trunk, only in the annual dev cycle.

Yeah, I can see different problems popping up, and alternative approaches.

I'm thinking let's try this to begin with, focusing on making it
easier to bump the version for our own sake (there's too much that's
hard-coded) and better documenting everything (all that's mentioned in
this thread). Off that, and seeing what happens in the ecosystem (and
what they ask for), we can evolve. Sound ok?

-
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

Re: [DISCUSS] Semantic versioning after 4.0

[Mick Semb Wever]

> Hmm, ok. I see some possible issues with this. You mention one possibility, 
> i.e. that downstream may end up releasing these versions for us? Which 
> potentially complicates our lives, whether we want it or not.
>
> Would this apply to only trunk, or to all existing major/minor releases?


Only trunk, only in the annual dev cycle.

Yeah, I can see different problems popping up, and alternative approaches.

I'm thinking let's try this to begin with, focusing on making it
easier to bump the version for our own sake (there's too much that's
hard-coded) and better documenting everything (all that's mentioned in
this thread). Off that, and seeing what happens in the ecosystem (and
what they ask for), we can evolve. Sound ok?

-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org

Re: [DISCUSS] Semantic versioning after 4.0

[Benedict Elliott Smith]

Hmm, ok. I see some possible issues with this. You mention one possibility, 
i.e. that downstream may end up releasing these versions for us? Which 
potentially complicates our lives, whether we want it or not. 

Would this apply to only trunk, or to all existing major/minor releases?

I wonder if there's a better way to implement this, perhaps simply with tags 
that are cut periodically and designed specifically for downstream to work with?

On 03/05/2021, 09:27, "Mick Semb Wever"  wrote:

> Sorry, I may be being dense, but it's not that I didn't parse your 
justification for it, but that I literally don't understand what the proposal 
is.


Ah, nothing more than every quarter we bump the minor version in build.xml
(the frequency is up for discussion)

-
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

Re: [DISCUSS] Semantic versioning after 4.0

[Mick Semb Wever]

> Sorry, I may be being dense, but it's not that I didn't parse your 
> justification for it, but that I literally don't understand what the proposal 
> is.


Ah, nothing more than every quarter we bump the minor version in build.xml
(the frequency is up for discussion)

-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org

Re: [DISCUSS] Semantic versioning after 4.0

[Benedict Elliott Smith]

Sorry, I may be being dense, but it's not that I didn't parse your 
justification for it, but that I literally don't understand what the proposal 
is.

On 03/05/2021, 08:30, "Mick Semb Wever"  wrote:

> I didn't really understand the unreleased versions proposal though.


Benedict, two brief example perspectives on it. This is all under the
"let's try, learn, evaluate" umbrella.

1)
Unreleased versions can give downstream more choices through the
annual development cycle than the binary choice of "latest snapshot"
or "a specific timestamped snapshot". An example, Reaper's tests
against trunk may find it too much overhead to keep up dev changes as
they land, but will benefit keeping up with quarterly increments.

2)
Being better at smooth version increments. Letting the version be
accurate to semver, and independent from the release cycle. This
should in turn get us better at knowing (and even automating) what
upgrades paths and compatibilities need to be tested through the dev
cycle. Our handling of versions through the tests is not ideal atm,
take for example the dtest upgrade manifest, or the jvm dtests which
can hardcode the upgrade paths within tests…)

-
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

Re: [DISCUSS] Semantic versioning after 4.0

[Mick Semb Wever]

> I didn't really understand the unreleased versions proposal though.


Benedict, two brief example perspectives on it. This is all under the
"let's try, learn, evaluate" umbrella.

1)
Unreleased versions can give downstream more choices through the
annual development cycle than the binary choice of "latest snapshot"
or "a specific timestamped snapshot". An example, Reaper's tests
against trunk may find it too much overhead to keep up dev changes as
they land, but will benefit keeping up with quarterly increments.

2)
Being better at smooth version increments. Letting the version be
accurate to semver, and independent from the release cycle. This
should in turn get us better at knowing (and even automating) what
upgrades paths and compatibilities need to be tested through the dev
cycle. Our handling of versions through the tests is not ideal atm,
take for example the dtest upgrade manifest, or the jvm dtests which
can hardcode the upgrade paths within tests…)

-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org