Re: [VOTE] Release Apache Cassandra 2.0.13

+1 On Fri, Mar 13, 2015 at 3:00 AM, Jonathan Ellis wrote: > +1 > > On Thu, Mar 12, 2015 at 8:55 PM, Jake Luciani wrote: > > > I propose the following artifacts for release as 2.0.13. > > > > sha1: 20593c24a9f8c07aff8f848f4b5774ed88ea4687 > > Git: > > > http://git-wip-us.apache.org/repos/asf?p=c

Re: [VOTE] Release Apache Cassandra 2.0.13

+1 发自我的 iPhone > 在 2015年3月13日，15:56，Sylvain Lebresne 写道： > > +1 > >> On Fri, Mar 13, 2015 at 3:00 AM, Jonathan Ellis wrote: >> >> +1 >> >>> On Thu, Mar 12, 2015 at 8:55 PM, Jake Luciani wrote: >>> >>> I propose the following artifacts for release as 2.0.13. >>> >>> sha1: 20593c24a9f8c07a

Re: [VOTE] Release Apache Cassandra 2.0.13

+1 On Thu, Mar 12, 2015 at 8:55 PM, Jake Luciani wrote: > I propose the following artifacts for release as 2.0.13. > > sha1: 20593c24a9f8c07aff8f848f4b5774ed88ea4687 > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.0.13-tentative > Artifacts: > https://rep

Question on updating Cassandra dependencies

Hello All, I have been told by my team that some of the cassandra dependencies have some vulnerabilities and should be upgraded. Specifically, Joda Time 1.6 should be upgraded to 2.7 Jackson 1.9.2 should be upgraded to 1.9.13 Is there any schedule or process of getting Cassandra updates to inc

Improving on release quality by iterating on our definition of done

Hi, I wrote a doc expounding on how tightening up our definition of when a ticket is done and merged can be used as a means of improving release quality. This is meant as a starting point for dis

Re: Question on updating Cassandra dependencies

Wow. It would be great if the Jackson dep could move up to 2.x. We'd even be willing to provide a PR for it. On Fri, Mar 13, 2015 at 12:22 PM, Joe Fasano wrote: > Hello All, > > I have been told by my team that some of the cassandra dependencies have > some vulnerabilities and > should be upgr

Re: Question on updating Cassandra dependencies

We don’t upgrade dependencies in minor C* releases, so 2.0 and 2.1 will have to stick to what’s already there. Feel free to open a JIRA issue for C* 3.0 to deal with upgrading all the dependencies, though. Just don’t create a PR - we cannot accept them. Just leave a comment with a link to your

Re: Question on updating Cassandra dependencies

From blogs I read that the estimate for release of 3.0 is April 2015. I'm not familiar with opening a JIRA, but would be great to open a general incident for updating all dependencies in 3.0. joe On 3/13/2015 3:30 PM, Aleksey Yeschenko wrote: We don’t upgrade dependencies in minor C* releases