+1
On Fri, Apr 20, 2012 at 12:38, Sylvain Lebresne wrote:
> The RC1 went well and we basically don't have any issue open left, so I
> think it's time to release the final Cassandra 1.1. I thus propose the
> following artifacts for release as 1.1.0.
>
> sha1: c671532825b9e05bd2b50e3aa2d1c5f5156d1c
Sounds good to me, +1.
--
Pavel Yaskevich
On Saturday 21 April 2012 at 01:07, Eric Evans wrote:
> On Fri, Apr 20, 2012 at 12:57 PM, Jonathan Ellis (mailto:jbel...@gmail.com)> wrote:
> > After the 0.7 release we decided to shoot for a fixed four-month
> > release cycle. I think now is a good
On Fri, Apr 20, 2012 at 12:57 PM, Jonathan Ellis wrote:
> After the 0.7 release we decided to shoot for a fixed four-month
> release cycle. I think now is a good time to re-evaluate this, and
> possibly change to target a six month cycle:
>
> - Speaking for DataStax, about half our time is spent
+1
On Fri, Apr 20, 2012 at 4:57 PM, Pavel Yaskevich wrote:
> +1
>
> On Saturday 21 April 2012 at 00:31, Brandon Williams wrote:
>
>> +1
>>
>> On Fri, Apr 20, 2012 at 12:38 PM, Sylvain Lebresne > (mailto:sylv...@datastax.com)> wrote:
>> > The RC1 went well and we basically don't have any issue ope
+1
On Saturday 21 April 2012 at 00:31, Brandon Williams wrote:
> +1
>
> On Fri, Apr 20, 2012 at 12:38 PM, Sylvain Lebresne (mailto:sylv...@datastax.com)> wrote:
> > The RC1 went well and we basically don't have any issue open left, so I
> > think it's time to release the final Cassandra 1.1. I
+1
On Fri, Apr 20, 2012 at 12:38 PM, Sylvain Lebresne wrote:
> The RC1 went well and we basically don't have any issue open left, so I
> think it's time to release the final Cassandra 1.1. I thus propose the
> following artifacts for release as 1.1.0.
>
> sha1: c671532825b9e05bd2b50e3aa2d1c5f5156
We've been working on the 'ooh, shiny' approach to upgrading.
Basically, once we see a new feature which will make life easier, better or
just give us an excuse to play we start the process of adoption.
Once we've managed to get our unit tests to pass, and updated our internal
process document
+1
is there any stats on customer adoption of new versions? I'd wonder if
people generally move to new versions every 4 months, as that could be
potentially painful for them as well. Given the amount of questions
regarding older versions still percolating, i'd guess the answer is
they'd be ok
After the 0.7 release we decided to shoot for a fixed four-month
release cycle. I think now is a good time to re-evaluate this, and
possibly change to target a six month cycle:
- Speaking for DataStax, about half our time is spent on maintenance.
Given this, a 3 month window just isn't much time
+1
On Fri, Apr 20, 2012 at 12:38 PM, Sylvain Lebresne wrote:
> The RC1 went well and we basically don't have any issue open left, so I
> think it's time to release the final Cassandra 1.1. I thus propose the
> following artifacts for release as 1.1.0.
>
> sha1: c671532825b9e05bd2b50e3aa2d1c5f5156
The RC1 went well and we basically don't have any issue open left, so I
think it's time to release the final Cassandra 1.1. I thus propose the
following artifacts for release as 1.1.0.
sha1: c671532825b9e05bd2b50e3aa2d1c5f5156d1c9f
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=sho
11 matches
Mail list logo