Re: [VOTE] Apache Cassandra Release Lifecycle

2019-10-04 Thread Scott Andreas 
There are two main benefits to agreeing on this:

1. Providing clarity for contributors on release phases – i.e., what types of 
changes are expected to land or be deferred during a particular point in that 
cycle.

2. Providing semantic clarity to users of Cassandra in terms of what they can 
expect from a given release.

The second one is more important. The document stands as a commitment between 
the Cassandra project and its users regarding what can be expected from each 
type of release. It defines GA releases as "recommended for production 
deployment for all users," setting a standard of quality that we aim to uphold 
together and that users can depend on. Affirming what it means for a release to 
be EOL, deprecated, or in maintenance signals importance of upgrading to a GA 
version.

The prerelease phases set expectations for us as contributors to produce a more 
stable release: what type of testing/validation is needed at what time, at 
which point interfaces/protocols solidify, when a release is considered feature 
complete, etc.

Creating clarity for ourselves will help us build a better database, and 
creating clarity for our users will help give them the confidence to run it.

I want to thank Sumanth for his work on this document and to everyone else 
who's contributed.

I support it (+1 nb).

– Scott


From: Stefan Podkowinski 
Sent: Tuesday, October 1, 2019 1:43 PM
To: dev@cassandra.apache.org
Subject: Re: [VOTE] Apache Cassandra Release Lifecycle

What exactly will be the implication of the outcome of this vote, in
case the content is agreed upon? What's the proposal of the voting?

The document seems to be informative rather then formal. It's verbose on
definitions that should be commonly understood or can only broadly
defined (what is alpha/beta/RC, GA for production, etc.), while at the
same time is unclear and weasel-wordy on our actual commitment and rules.


On 30.09.19 20:51, sankalp kohli wrote:
> Hi,
>  We have discussed in the email thread[1] about Apache Cassandra Release
> Lifecycle. We came up with a doc[2] for it. Please vote on it if you agree
> with the content of the doc[2].
>
> Thanks,
> Sankalp
>
> [1]
> https://lists.apache.org/thread.html/c610b23f9002978636b66d09f0e0481ed3de9b78895050da22c91c6f@%3Cdev.cassandra.apache.org%3E
> [2]
> https://docs.google.com/document/d/1bS6sr-HSrHFjZb0welife6Qx7u3ZDgRiAoENMLYlfz8/edit#heading=h.633eppni91tw
>

-
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: time for a release?

2019-10-04 Thread DuyHai Doan 
+1 too (non binding)

On Fri, Oct 4, 2019 at 10:33 PM Scott Andreas  wrote:
>
> +1nb for me for the 3.x releases.
>
> The user-facing issues resolved in 2.2 are slimmer and relatively minor (just 
> 15225, 15050, 15045, 15041), but if it makes sense to release all three 
> together, sounds good to me.
>
> – Scott
>
> On 10/4/19, 11:00 AM, "Jon Haddad"  wrote:
>
> It's been a while since we did a release and I think there's enough in 
> here
> to put one out.
>
> 2.2.15 changes:
> 
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CASSANDRA%20AND%20fixVersion%20%3D%202.2.15%20and%20status%20%3D%20Resolved%20
>
> 3.0.19 changes:
> 
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CASSANDRA%20AND%20fixVersion%20%3D%203.0.19%20and%20status%20%3D%20Resolved%20%20
>
> 3.11.5 changes:
> 
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CASSANDRA%20AND%20fixVersion%20%3D%203.11.5%20and%20status%20%3D%20Resolved%20
>
> Any reason not to put this up for a vote?  If I don't hear anything by
> Monday I'll start a vote thread.
>
> Jon
>
>

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

Re: time for a release?

2019-10-04 Thread Scott Andreas 
+1nb for me for the 3.x releases.

The user-facing issues resolved in 2.2 are slimmer and relatively minor (just 
15225, 15050, 15045, 15041), but if it makes sense to release all three 
together, sounds good to me.

– Scott

On 10/4/19, 11:00 AM, "Jon Haddad"  wrote:

It's been a while since we did a release and I think there's enough in here
to put one out.

2.2.15 changes:

https://issues.apache.org/jira/issues/?jql=project%20%3D%20CASSANDRA%20AND%20fixVersion%20%3D%202.2.15%20and%20status%20%3D%20Resolved%20

3.0.19 changes:

https://issues.apache.org/jira/issues/?jql=project%20%3D%20CASSANDRA%20AND%20fixVersion%20%3D%203.0.19%20and%20status%20%3D%20Resolved%20%20

3.11.5 changes:

https://issues.apache.org/jira/issues/?jql=project%20%3D%20CASSANDRA%20AND%20fixVersion%20%3D%203.11.5%20and%20status%20%3D%20Resolved%20

Any reason not to put this up for a vote?  If I don't hear anything by
Monday I'll start a vote thread.

Jon

time for a release?

2019-10-04 Thread Jon Haddad 
It's been a while since we did a release and I think there's enough in here
to put one out.

2.2.15 changes:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20CASSANDRA%20AND%20fixVersion%20%3D%202.2.15%20and%20status%20%3D%20Resolved%20

3.0.19 changes:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20CASSANDRA%20AND%20fixVersion%20%3D%203.0.19%20and%20status%20%3D%20Resolved%20%20

3.11.5 changes:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20CASSANDRA%20AND%20fixVersion%20%3D%203.11.5%20and%20status%20%3D%20Resolved%20

Any reason not to put this up for a vote?  If I don't hear anything by
Monday I'll start a vote thread.

Jon

ApacheCon Europe 2019 talks which are relevant to Apache Cassandra

2019-10-04 Thread myrle 

Dear Apache Cassandra committers,

In a little over 2 weeks time, ApacheCon Europe is taking place in 
Berlin. Join us from October 22 to 24 for an exciting program and lovely 
get-together of the Apache Community.


We are also planning a hackathon.  If your project is interested in 
participating, please enter yourselves here: 
https://cwiki.apache.org/confluence/display/COMDEV/Hackathon


The following talks should be especially relevant for you:

**

 * *

   
https://aceu19.apachecon.com/session/kafka-cassandra-and-kubernetes-scale-real-time-anomaly-detection-19-billion-events-day

 *

   
https://aceu19.apachecon.com/session/supporting-open-source-house-experience-cassandra

 * 
*https://aceu19.apachecon.com/session/extensible-autonomous-transactions-world-microservices-using-apache-kafka*
   *

*

**

 * *

   
https://aceu19.apachecon.com/session/patterns-and-anti-patterns-running-apache-bigdata-projects-kubernetes

 *

   https://aceu19.apachecon.com/session/fast-federated-sql-apache-calcite

 *

   
https://aceu19.apachecon.com/session/open-source-big-data-tools-accelerating-physics-research-cern

 *

   https://aceu19.apachecon.com/session/ui-dev-big-data-world-using-open-source

 * 
*https://aceu19.apachecon.com/session/maintaining-java-library-light-new-java-release-train*
   *

**

*

Furthermore there will be a whole conference track on community topics: 
Learn how to motivate users to contribute patches, how the board of 
directors works, how to navigate the Incubator and much more: ApacheCon 
Europe 2019 Community track 


Tickets are available here  – 
for Apache Committers we offer discounted tickets.  Prices will be going 
up on October 7th, so book soon.


Please also help spread the word and make ApacheCon Europe 2019 a success!

We’re looking forward to welcoming you at #ACEU19!

Best,

Your ApacheCon team