because cassandra 1.0 is not sufficiently stable, what about to make
cassandra 1.0 default download and add bottom line - cassandra 1.0 is
also available.
I seen this in other projects.
Oh my this all sounds very alarming. Should I be confused? Or even the
other way around?
On 19/05/2012 08:08, Radim Kolar wrote:
because cassandra 1.0 is not sufficiently stable, what about to make
cassandra 1.0 default download and add bottom line - cassandra 1.0 is
also available.
I seen
message was wrong, It should be cass 1.1 vs 1.0. Cassandra 1.1 needs
some time to stabilize. It took months to get cassandra 1.0 stable after
it was released.
Reworked schema changes in cass 1.1 produces some really weird bugs like
disappearing entire keyspace (data are still there). I think
Kolar wrote:
message was wrong, It should be cass 1.1 vs 1.0. Cassandra 1.1 needs
some time to stabilize. It took months to get cassandra 1.0 stable
after it was released.
Reworked schema changes in cass 1.1 produces some really weird bugs
like disappearing entire keyspace (data are still
Hi all,
Can anyone remind me what the release date for 1.0 is. I wrote a Python
ORM mapper
similar to the GAE Models sometime ago and I want to brush it up and
opensource it
within the same period.
Thanks.
The release vote is currently running, so, any time now. I believe the
original target release date was October 8th; but that fell on a weekend and
it's been delayed by a couple of regressions.
Regards,
Nick Telford
On 13 October 2011 14:24, Iroiso iro...@live.com wrote:
Hi all,
Can anyone
On Thu, Sep 8, 2011 at 2:51 PM, Jonathan Ellis jbel...@gmail.com wrote:
On Thu, Sep 8, 2011 at 5:14 AM, Sylvain Lebresne sylv...@datastax.com wrote:
To have things moving, I propose we aim for calling the vote on a first beta
release at the end of next week (say next Thursday for instance).
On Fri, Sep 9, 2011 at 6:43 AM, Sylvain Lebresne sylv...@datastax.com wrote:
On the 1.0 housekeeping business, I've created two new svn branches:
* 1.0.0: this is what will be ultimately released as the 1.0 final
* 1.0: this is for stuff that don't made the freeze but should go in
1.0.1.
testing/debugging.
Allow me to remind everyone that this release will be called Apache Cassandra
1.0. Whether we want it or not, people will see special meaning in that
number and have higher expectations. We *need* to have a release as solid as
possibly can. So please, do help testing as much
Ladies and Gentlemen,
Cassandra 0.8 is now out and we'll hopefully soon have the first minor release
on that branch out too. It is now time to think of the next iteration, aka
Apache Cassandra 1.0 (sounds amazing...).
The 0.8 release was our first release on our new fixed 4 months release
+1
On Thu, Jun 16, 2011 at 7:36 AM, Sylvain Lebresne sylv...@datastax.com wrote:
Ladies and Gentlemen,
Cassandra 0.8 is now out and we'll hopefully soon have the first minor release
on that branch out too. It is now time to think of the next iteration, aka
Apache Cassandra 1.0 (sounds
sylv...@datastax.com
wrote:
Ladies and Gentlemen,
Cassandra 0.8 is now out and we'll hopefully soon have the first minor
release
on that branch out too. It is now time to think of the next iteration, aka
Apache Cassandra 1.0 (sounds amazing...).
The 0.8 release was our first release on our
On Thu, 2011-06-16 at 09:15 -0700, Ryan King wrote:
I think maybe 4 months was too short? Do we optimistically want to try
that again or plan on taking a bit more time?
I think 4 months is about the right amount of time.
Also, our upgrade story is better than it has ever been, which changes
On Thu, 2011-06-16 at 16:36 +0200, Sylvain Lebresne wrote:
Sticking to that 4 months schedule, I propose the following deadlines:
- September 8th: feature freeze
- October 8th: release (tentative date)
+1
--
Eric Evans
eev...@rackspace.com
and we'll hopefully soon have the first minor release
on that branch out too. It is now time to think of the next iteration, aka
Apache Cassandra 1.0 (sounds amazing...).
The 0.8 release was our first release on our new fixed 4 months release
schedule. 0.7.0 was released January 9th and 0.8.0
There is already so much stuff on the 1.0 branch that I don't think 4 month to
feature freeze is a problem.
Assuming big stuff like new sstable format will go into 1.0, I am more
concerned about the 1 month from freeze to release.
Regards,
Terje
On 17 Jun 2011, at 01:39, Eric Evans
16 matches
Mail list logo
