Re: Announcements List

2011-07-20 Thread Ed Anuff
+1 that's a great idea On Wed, Jul 20, 2011 at 10:19 AM, Jonathan Ellis wrote: > I'd love to put a "Planet Cassandra" aggregator together. > > On Wed, Jul 20, 2011 at 12:13 PM, Ed Anuff wrote: >> I think that what's being asked for isn't so much announcements as >> some sort of way of communica

Re: Announcements List

2011-07-20 Thread David Boxenhorn
Edward, by "noise" I mean talk between users, or even developers, that's not hard information about Cassandra. (I don't mean to demean talk between users or developers, that is indeed the place to go if you want to be part of the conversation.) I don't consider announcements about upcoming features

Re: Announcements List

2011-07-20 Thread Edward Capriolo
On Wed, Jul 20, 2011 at 12:48 PM, David Boxenhorn wrote: > I am not going to argue the point, because it's not really the point that I > wanted to make. Maybe I'm an atypical user. > > The point I wanted to make is that there should be someplace for users to > go > to find out what's going on with

Re: Announcements List

2011-07-20 Thread David Boxenhorn
Ed, that's exactly what I want. A blog format works for me too. Cassandra is *far* from being a black box, and users have to be quite educated about Cassandra internals in order to make decisions. Here are some examples of things I'd like to know, from concrete to abstract: 1. New releases 2. Bug

Re: Announcements List

2011-07-20 Thread Jonathan Ellis
I'd love to put a "Planet Cassandra" aggregator together. On Wed, Jul 20, 2011 at 12:13 PM, Ed Anuff wrote: > I think that what's being asked for isn't so much announcements as > some sort of way of communicating or summarizing roadmap.  However, in > practical matters, I'm not sure how this can

Re: Announcements List

2011-07-20 Thread Ed Anuff
I think that what's being asked for isn't so much announcements as some sort of way of communicating or summarizing roadmap. However, in practical matters, I'm not sure how this can be done in a mailing list form. Anything that gets "announced" as roadmap is either so far along that it's not road

Re: Announcements List

2011-07-20 Thread Edward Capriolo
On Wed, Jul 20, 2011 at 12:28 PM, David Boxenhorn wrote: > Not true. I am a user. I consider this to be effectively the same as > deprecating supercolumns (with support for the old API for backward > compatibility). The fact that it is in the presentation that I linked to - > from a DataStax emplo

Re: Announcements List

2011-07-20 Thread David Boxenhorn
I am not going to argue the point, because it's not really the point that I wanted to make. Maybe I'm an atypical user. The point I wanted to make is that there should be someplace for users to go to find out what's going on with Cassandra, with out all the noise of the user and dev lists, or JIRA

Re: Announcements List

2011-07-20 Thread Jonathan Ellis
You missed the point completely, then. We recommend not using Supercolumns if you don't know what you're doing, because almost everyone who does is doing it for the wrong reasons. If you are using Supercolumns for the right reasons (or even the wrong ones) you don't need to worry because the API

Re: Announcements List

2011-07-20 Thread David Boxenhorn
Not true. I am a user. I consider this to be effectively the same as deprecating supercolumns (with support for the old API for backward compatibility). The fact that it is in the presentation that I linked to - from a DataStax employee! - with essentially the same message (i.e. don't use them if y

Re: Announcements List

2011-07-20 Thread Jonathan Ellis
That's exactly the kind of thing that *shouldn't* be on an announce list (and stay on the dev list), precisely because it deals with internals that users don't care about. On Wed, Jul 20, 2011 at 11:18 AM, David Boxenhorn wrote: > I would like to see this list also used for announcing upcoming fe

Re: Announcements List

2011-07-20 Thread David Boxenhorn
I would like to see this list also used for announcing upcoming features. At some point a decision is made that some future version will include some important feature. I don't want that information to be buried in a JIRA ticket or a user/dev list discussion. For example, I was surprised to learn,