Re: time for a release?
> Any reason not to put this up for a vote? If I don't hear anything by > Monday I'll start a vote thread. We're still in the position where only four people in the project: Michael, Sylvain, Jake, and Eric; can cut, stage, and propose a release. Is it time to add more people to our KEYS file? This will have the consequence that debian users will have to re-add it. But maybe we can accept a window, from now until the first 4.0 rc, where all committers are free to open a PR to add themselves to the KEYS file? https://www-us.apache.org/dist/cassandra/KEYS https://www.apache.org/dev/release-signing http://cassandra.apache.org/doc/latest/getting_started/installing.html#installation-from-debian-packages - To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
Re: time for a release?
+1 from me. On Fri, Oct 4, 2019 at 4:47 PM DuyHai Doan wrote: > +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?
+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?
+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?
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
Re: Time for a release candidate?
+1 On Aug 17, 2013 8:15 PM, Jonathan Ellis jbel...@gmail.com wrote: Added a short description. On Mon, Aug 12, 2013 at 12:40 AM, Dave Brosius dbros...@mebigfatguy.com wrote: On 08/11/2013 10:51 PM, Brandon Williams wrote: On Sun, Aug 11, 2013 at 9:35 PM, Jonathan Ellis jbel...@gmail.com wrote: We hadn't actually set vnodes to be on by default, which we should do after having 1.2 default to old single token per node. Fixed in CASSANDRA-5869 so let's roll an rc2. Let's get https://issues.apache.org/jira/browse/CASSANDRA-5856 solved first. -Brandon There is a blank README.txt file in the conf/triggers directory. (or perhaps written in lemon-ink). -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced
Re: Time for a release candidate?
We hadn't actually set vnodes to be on by default, which we should do after having 1.2 default to old single token per node. Fixed in CASSANDRA-5869 so let's roll an rc2. On Sat, Aug 3, 2013 at 2:48 PM, Jonathan Ellis jbel...@gmail.com wrote: We've cleaned out everything tagged for rc1, anything else we need to do before rolling it up for a vote? -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced
Re: Time for a release candidate?
On Sun, Aug 11, 2013 at 9:35 PM, Jonathan Ellis jbel...@gmail.com wrote: We hadn't actually set vnodes to be on by default, which we should do after having 1.2 default to old single token per node. Fixed in CASSANDRA-5869 so let's roll an rc2. Let's get https://issues.apache.org/jira/browse/CASSANDRA-5856 solved first. -Brandon
Re: Time for a release candidate?
On 08/11/2013 10:51 PM, Brandon Williams wrote: On Sun, Aug 11, 2013 at 9:35 PM, Jonathan Ellis jbel...@gmail.com wrote: We hadn't actually set vnodes to be on by default, which we should do after having 1.2 default to old single token per node. Fixed in CASSANDRA-5869 so let's roll an rc2. Let's get https://issues.apache.org/jira/browse/CASSANDRA-5856 solved first. -Brandon There is a blank README.txt file in the conf/triggers directory. (or perhaps written in lemon-ink).
Re: Time for a release candidate?
+1. Also I think it is time for creating cassandra-2.0 branching. On Sat, Aug 3, 2013 at 2:48 PM, Jonathan Ellis jbel...@gmail.com wrote: We've cleaned out everything tagged for rc1, anything else we need to do before rolling it up for a vote? -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced -- Yuki Morishita t:yukim (http://twitter.com/yukim)
