[VOTE] Release Apache Cassandra 3.0.20

[Mick Semb Wever]

Proposing the test build of Cassandra 3.0.20 for release.

sha1: 89edf5073ba4181dd2f70294cdbcb47f5a45c82e
Git: 
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.20-tentative
Maven Artifacts: 
https://repository.apache.org/content/repositories/orgapachecassandra-1193/org/apache/cassandra/cassandra-all/3.0.20/

The Source and Build Artifacts, and the Debian and RPM packages and 
repositories, are available here: 
https://dist.apache.org/repos/dist/dev/cassandra/3.0.20/

The vote will be open for 72 hours (longer if needed). Everyone who has tested 
the build is invited to vote. Votes by PMC members are considered binding. A 
vote passes if there are at least three binding +1s.

Again note the release process is undergoing improvements to deal with 
sha256|512 checksums and to use the ASF dev dist staging location. Please be 
extra critical. The deb and rpm repositories are also now available to verify 
before the vote.


[1]: CHANGES.txt: 
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/3.0.20-tentative
[2]: NEWS.txt: 
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/3.0.20-tentative

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

[VOTE] Release Apache Cassandra 3.11.6

[Mick Semb Wever]

Proposing the test build of Cassandra 3.11.6 for release.

sha1: cb779ab9a631c13a245926f55320392c4468c6f0
Git: 
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.11.6-tentative
Maven Artifacts: 
https://repository.apache.org/content/repositories/orgapachecassandra-1194/org/apache/cassandra/cassandra-all/3.11.6/

The Source and Build Artifacts, and the Debian and RPM packages and 
repositories, are available here: 
https://dist.apache.org/repos/dist/dev/cassandra/3.11.6/

The vote will be open for 72 hours (longer if needed). Everyone who has tested 
the build is invited to vote. Votes by PMC members are considered binding. A 
vote passes if there are at least three binding +1s.

Again note the release process is undergoing improvements to deal with 
sha256|512 checksums and to use the ASF dev dist staging location. Please be 
extra critical. The deb and rpm repositories are also now available to verify 
before the vote.


[1]: CHANGES.txt: 
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/3.11.6-tentative
[2]: NEWS.txt: 
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/3.11.6-tentative

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

Libraries update

[Ekaterina Dimitrova]

Hello everyone,
I was looking into some library updates these dates as per user requests.
This made me think about one thing. As we approach the new version release,
were the versions of the libraries cassandra depends on sanitized in any
way? Is there an overall view or plans for updates? Or is it done on a
case by case basis?
If it is not done, do you think it would be a good idea to get a certain
view on those and see what can be easily updated? I know it is late for big
rewrites but at least maybe we can update to new versions those which don't
introduce big changes?
Any thoughts? Objections?

Ekaterina Dimitrova | Software Engineer
ekaterina.dimitr...@datastax.com | datastax.com

Re: Libraries update

[Nate McCall]

I would love to see an audit and rough plan on maintenance and evaluation
criteria, etc added to the wiki for discussion. We've had a couple of users
complain about library versions when including the aftifact as a dependency
(even though we don't support this, a lot of people do it). It would be
cool to have something to point to at the very least.

Thanks for bringing this up!!

On Wed, Feb 12, 2020 at 8:44 AM Ekaterina Dimitrova <
ekaterina.dimitr...@datastax.com> wrote:

> Hello everyone,
> I was looking into some library updates these dates as per user requests.
> This made me think about one thing. As we approach the new version release,
> were the versions of the libraries cassandra depends on sanitized in any
> way? Is there an overall view or plans for updates? Or is it done on a
> case by case basis?
> If it is not done, do you think it would be a good idea to get a certain
> view on those and see what can be easily updated? I know it is late for big
> rewrites but at least maybe we can update to new versions those which don't
> introduce big changes?
> Any thoughts? Objections?
>
> Ekaterina Dimitrova | Software Engineer
> ekaterina.dimitr...@datastax.com | datastax.com
> <
> http://datastax.com/?utm_campaign=FY20Q2_CONSTELLATION&utm_+medium=email&utm_source=signature
> >
>

Re: Libraries update

[Nate McCall]

Quick answer to your question though is no, it's been entirely adhoc.

On Wed, Feb 12, 2020 at 8:50 AM Nate McCall  wrote:

> I would love to see an audit and rough plan on maintenance and evaluation
> criteria, etc added to the wiki for discussion. We've had a couple of users
> complain about library versions when including the aftifact as a dependency
> (even though we don't support this, a lot of people do it). It would be
> cool to have something to point to at the very least.
>
> Thanks for bringing this up!!
>
> On Wed, Feb 12, 2020 at 8:44 AM Ekaterina Dimitrova <
> ekaterina.dimitr...@datastax.com> wrote:
>
>> Hello everyone,
>> I was looking into some library updates these dates as per user requests.
>> This made me think about one thing. As we approach the new version
>> release,
>> were the versions of the libraries cassandra depends on sanitized in any
>> way? Is there an overall view or plans for updates? Or is it done on a
>> case by case basis?
>> If it is not done, do you think it would be a good idea to get a certain
>> view on those and see what can be easily updated? I know it is late for
>> big
>> rewrites but at least maybe we can update to new versions those which
>> don't
>> introduce big changes?
>> Any thoughts? Objections?
>>
>> Ekaterina Dimitrova | Software Engineer
>> ekaterina.dimitr...@datastax.com | datastax.com
>> <
>> http://datastax.com/?utm_campaign=FY20Q2_CONSTELLATION&utm_+medium=email&utm_source=signature
>> >
>>
>

Re: Libraries update

[Deepak Vohra]

 
Dependency management is discussed at Documentation

| 
| 
|  | 
Documentation

The Apache Cassandra database is the right choice when you need scalability and 
high availability without compro...
 |

 |

 |



On Tuesday, February 11, 2020, 07:44:15 p.m. UTC, Ekaterina Dimitrova 
 wrote:  
 
 Hello everyone,
I was looking into some library updates these dates as per user requests.
This made me think about one thing. As we approach the new version release,
were the versions of the libraries cassandra depends on sanitized in any
way? Is there an overall view or plans for updates? Or is it done on a
case by case basis?
If it is not done, do you think it would be a good idea to get a certain
view on those and see what can be easily updated? I know it is late for big
rewrites but at least maybe we can update to new versions those which don't
introduce big changes?
Any thoughts? Objections?

Ekaterina Dimitrova | Software Engineer
ekaterina.dimitr...@datastax.com | datastax.com

  

Re: Libraries update

[Nate McCall]

Good point Deepak - we do have:
http://cassandra.apache.org/doc/latest/development/dependencies.html

But we dont have details or process written down.

On Wed, Feb 12, 2020 at 9:02 AM Deepak Vohra 
wrote:

>
> Dependency management is discussed at Documentation
>
> |
> |
> |  |
> Documentation
>
> The Apache Cassandra database is the right choice when you need
> scalability and high availability without compro...
>  |
>
>  |
>
>  |
>
>
>
> On Tuesday, February 11, 2020, 07:44:15 p.m. UTC, Ekaterina Dimitrova <
> ekaterina.dimitr...@datastax.com> wrote:
>
>  Hello everyone,
> I was looking into some library updates these dates as per user requests.
> This made me think about one thing. As we approach the new version release,
> were the versions of the libraries cassandra depends on sanitized in any
> way? Is there an overall view or plans for updates? Or is it done on a
> case by case basis?
> If it is not done, do you think it would be a good idea to get a certain
> view on those and see what can be easily updated? I know it is late for big
> rewrites but at least maybe we can update to new versions those which don't
> introduce big changes?
> Any thoughts? Objections?
>
> Ekaterina Dimitrova | Software Engineer
> ekaterina.dimitr...@datastax.com | datastax.com
> <
> http://datastax.com/?utm_campaign=FY20Q2_CONSTELLATION&utm_+medium=email&utm_source=signature
> >
>

Re: Libraries update

[Tomo Suzuki]

> do you think it would be a good idea to get a certain
view on those and see what can be easily updated?

Yes!
With more up-to-date dependencies, Cassandra will work with other open
source software smoothly. Looking forward.

On Tue, Feb 11, 2020 at 2:44 PM Ekaterina Dimitrova
 wrote:
>
> Hello everyone,
> I was looking into some library updates these dates as per user requests.
> This made me think about one thing. As we approach the new version release,
> were the versions of the libraries cassandra depends on sanitized in any
> way? Is there an overall view or plans for updates? Or is it done on a
> case by case basis?
> If it is not done, do you think it would be a good idea to get a certain
> view on those and see what can be easily updated? I know it is late for big
> rewrites but at least maybe we can update to new versions those which don't
> introduce big changes?
> Any thoughts? Objections?
>
> Ekaterina Dimitrova | Software Engineer
> ekaterina.dimitr...@datastax.com | datastax.com
> 



-- 
Regards,
Tomo

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

Re: Libraries update

[Deepak Vohra]

 For specific versions of dependencies scroll down for the Compile Dependencies 
and Managed Dependencies at Maven Repository: org.apache.cassandra » 
cassandra-all » 4.0-alpha3


| 
| 
| 
|  |  |

 |

 |
| 
|  | 
Maven Repository: org.apache.cassandra » cassandra-all » 4.0-alpha3


 |

 |

 |



Or, if not these, what other dependencies are being referred to?thanks,Deepak   
 On Tuesday, February 11, 2020, 08:09:41 p.m. UTC, Tomo Suzuki 
 wrote:  
 
 > do you think it would be a good idea to get a certain
view on those and see what can be easily updated?

Yes!
With more up-to-date dependencies, Cassandra will work with other open
source software smoothly. Looking forward.

On Tue, Feb 11, 2020 at 2:44 PM Ekaterina Dimitrova
 wrote:
>
> Hello everyone,
> I was looking into some library updates these dates as per user requests.
> This made me think about one thing. As we approach the new version release,
> were the versions of the libraries cassandra depends on sanitized in any
> way? Is there an overall view or plans for updates? Or is it done on a
> case by case basis?
> If it is not done, do you think it would be a good idea to get a certain
> view on those and see what can be easily updated? I know it is late for big
> rewrites but at least maybe we can update to new versions those which don't
> introduce big changes?
> Any thoughts? Objections?
>
> Ekaterina Dimitrova | Software Engineer
> ekaterina.dimitr...@datastax.com | datastax.com
> 



-- 
Regards,
Tomo

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

  

Re: Feedback from the last Apache Cassandra Contributor Meeting

[Patrick McFadin]

Survey is closed. Thank you everyone that took time to give your feedback.
Here are the results: https://www.surveymonkey.com/results/SM-7YTMZYLT7/

Based on the feedback, these meetings are useful and this seems to be the
ideal format:

1 Hour scheduled
Monthly
Rotate through 10AM-1PM PST to try to cover as many time zones as possible.

Excellent suggestion was to pre-determine a scribe for the meeting notes.
I'll add that to the meeting setup in cwiki.

I'll get the meetings calendared for the next 6 months based on those
criteria and update the cwiki as needed.

Thanks again!

Patrick

On Mon, Feb 10, 2020 at 9:28 AM Patrick McFadin  wrote:

> Just a Monday reminder on the survey link I sent. I got a few responses
> but could use a few more to give us some decent N. If you have < 5minutes
> today, I would appreciate your feedback. I'll keep it open until tomorrow
> and then send results.
>
> Patrick
>
> On Mon, Feb 3, 2020 at 4:21 PM Patrick McFadin  wrote:
>
>> Hi everyone,
>>
>> One action item I took from our first contributor meeting was gather
>> feedback for the next meetings. I've created a short survey if you would
>> like to offer feedback. I'll let it run for the week and report back on the
>> results.
>>
>> https://www.surveymonkey.com/r/C95B7ZP
>>
>> Thanks,
>>
>> Patrick
>>
>

Re: Feedback from the last Apache Cassandra Contributor Meeting

[Scott Andreas]

Thank you, Patrick!

> On Feb 11, 2020, at 3:05 PM, Patrick McFadin  wrote:
> 
> Survey is closed. Thank you everyone that took time to give your feedback.
> Here are the results: https://www.surveymonkey.com/results/SM-7YTMZYLT7/
> 
> Based on the feedback, these meetings are useful and this seems to be the
> ideal format:
> 
> 1 Hour scheduled
> Monthly
> Rotate through 10AM-1PM PST to try to cover as many time zones as possible.
> 
> Excellent suggestion was to pre-determine a scribe for the meeting notes.
> I'll add that to the meeting setup in cwiki.
> 
> I'll get the meetings calendared for the next 6 months based on those
> criteria and update the cwiki as needed.
> 
> Thanks again!
> 
> Patrick
> 
>> On Mon, Feb 10, 2020 at 9:28 AM Patrick McFadin  wrote:
>> 
>> Just a Monday reminder on the survey link I sent. I got a few responses
>> but could use a few more to give us some decent N. If you have < 5minutes
>> today, I would appreciate your feedback. I'll keep it open until tomorrow
>> and then send results.
>> 
>> Patrick
>> 
>>> On Mon, Feb 3, 2020 at 4:21 PM Patrick McFadin  wrote:
>>> 
>>> Hi everyone,
>>> 
>>> One action item I took from our first contributor meeting was gather
>>> feedback for the next meetings. I've created a short survey if you would
>>> like to offer feedback. I'll let it run for the week and report back on the
>>> results.
>>> 
>>> https://www.surveymonkey.com/r/C95B7ZP
>>> 
>>> Thanks,
>>> 
>>> Patrick
>>> 
>> 

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