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 you're just starting), is more evidence that users should care about it.
On Wed, Jul 20, 2011 at 7:21 PM, Jonathan Ellis <jbel...@gmail.com> wrote: > 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 <da...@citypath.com> > wrote: > > 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, by accident, from > > http://www.slideshare.net/mattdennis/cassandra-antipatterns , that > > supercolumns will be replaced, internally, by composite columns. This is > > something that we've discussed in the past, and that I have advocated > > myself, but until now I have seen no indication that it would be done, or > > that it was even viewed favorably by a consensus of decision makers. > > > > > > On Mon, Jul 18, 2011 at 6:52 PM, Nick Bailey <n...@datastax.com> wrote: > > > >> DataStax has had requests for something like this. It seems like > >> something that would be generally useful for the community though. > >> > >> Regarding twitter, I'm not sure a twitter account should be required > >> to get that information. I think you can follow a twitter account as > >> an rss feed though, so that might be a solution. That and the google > >> alert or email filter solutions just seem to be introducing more > >> difficulty for anyone trying to get that information. Perhaps the > >> demand for this isn't as high as I am imagining though. > >> > >> My opinion on the list if we decide to go with that is that only > >> committers would be able to post to it and yes it would go to the > >> users list as well. > >> > >> On Mon, Jul 18, 2011 at 10:32 AM, Sylvain Lebresne < > sylv...@datastax.com> > >> wrote: > >> > I have mixed feeling about that. > >> > > >> > On the one side, I agree with Gary that it doesn't add any real value. > >> > There is twitter, > >> > and we use consistent tagged subjects for release email, so it's easy > >> > to subscribe > >> > to the user list and set up a filter. > >> > > >> > That being said, I could understand that some people may find it > >> > cleaner to have a > >> > separate announce list and it is not something unheard of, so I'm ok > >> > with that if enough > >> > people thinks it's a good idea. But I think there is at least 2 > >> > questions that come along: > >> > - should it be moderated ? > >> > - should announces still be sent to the user list ? > >> > > >> > -- > >> > Sylvain > >> > > >> > On Mon, Jul 18, 2011 at 4:50 PM, Gary Dusbabek <gdusba...@gmail.com> > >> wrote: > >> >> Following @cassandra on twitter or a google alert would be simple > enough > >> I > >> >> think. > >> >> > >> >> Gary. > >> >> > >> >> On Mon, Jul 18, 2011 at 14:26, Nick Bailey <n...@datastax.com> > wrote: > >> >> > >> >>> What do we think about having a separate mailing list for just > >> >>> cassandra related announcements. The main purpose being announcing > new > >> >>> releases once they pass a vote and are put up on the website. I > think > >> >>> there is a desire for a way to be informed when new releases are > >> >>> available without sifting through the dev or users mailing lists. > >> >>> > >> >> > >> > > >> > > > > > > -- > Jonathan Ellis > Project Chair, Apache Cassandra > co-founder of DataStax, the source for professional Cassandra support > http://www.datastax.com >
