You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@cassandra.apache.org by Oleg Tsvinev <ol...@gmail.com> on 2011/01/10 20:44:11 UTC
Cassandra 0.7.0 Release in Riptano public repository?
Hi,
http://cassandra.apache.org/download/ shows that
"The latest stable release of Apache Cassandra is 0.7.0 (released on
2011-01-09). If you're just starting out, download this one."
However, I don't see this version in Riptano public repository. The latest
there is still 0.7.0-rc4.
Is there any chance to get it from there?
Thank you,
Oleg
Re: Cassandra 0.7.0 Release in Riptano public repository?
Posted by Rauan Maemirov <ra...@maemirov.com>.
When I try `rpm -i riptano-release-5-1.el6.noarch.rpm`, it just freeze. Does
repository work?
2011/1/12 Michael Fortin <mi...@m410.us>
> Thanks for your thoughtful and detailed replies Eric, it's much
> appreciated.
>
> Mike
>
> On Jan 11, 2011, at 11:23 AM, Eric Evans wrote:
>
> > On Tue, 2011-01-11 at 09:23 -0500, Michael Fortin wrote:
> >> This my understanding of 0.* releases.
> >> - They're not considered production ready by the maintainers
> >> - They subject to changes that break backwards compatibility
> >> - Generally poorly documented because the api is so volatile
> >> - Previous releases are unsupported
> >>
> >> for 1.* releases
> >> - The maintainer is saying this is tested and production ready,
> >> sometimes also marked as Final for GA
> >> - Minor releases do not break backward compatibility
> >> - The major and minor release have some level of support, with open
> >> source, that usually means docs and mailing lists but they should be
> >> very active.
> >> - thoroughly documented
> >
> > FWIW, your interpretation of what it means to be 1.0, is not wholly
> > unique, but it's far from universal either.
> >
> >> Sorting through the issue tracker is a little to fine grained to get a
> >> big picture view of where cassandra is going.
> >
> > Sorry, I should have been more clear here.
> >
> > The closest we have to a roadmap are the tickets that are marked as
> > blocking the next release, you shouldn't have to do any digging, they're
> > all available in one view here:
> >
> >
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=12310865&fixfor=12314820
> >
> > But, it's pretty fluid for the first few months after a new release.
> >
> >> And, just to be clear, I'm not questioning the maintainers approach,
> >> just humbling asking for a little more clarification. Cassandra is
> >> awesome, and I'm itching to use it on some production projects where I
> >> think it would be a great fit, but 0.* designation scares me a little.
> >> Of course, a hastily released 1.* would be worse.
> >
> > I understand, but what I'm saying is a "1.0" release in this context
> > carries special significance that just doesn't map well to open source
> > projects. And, in addition to being subjective, your criteria differs
> > from that of many people. It might make things easier to just version
> > some future release 1.0 and be done with it, but I'd rather be honest
> > with you.
> >
> > This is honest:
> >
> > * We treated the Google code dump in 2008 as 0.1.0 (though no formal
> > release was made).
> > * We likewise treated the Apache code dump in 2009 as 0.2.0 (again, no
> > formal release).
> > * We called the first release under the Apache Incubator 0.3.0.
> > * We just now released 0.7.0.
> > * We maintain backward compatibility between the "minor" and "revision",
> > that is 0.6.1, 0.6.2, 0.6.3, etc.
> >
> > This is why I said my preference would be to just drop the leading 0.
> > We've been using the minor like a major, and the revision like a minor,
> > (and we haven't had need for a revision). We've had 7 major releases,
> > (5 if you only want to count what's happened under Apache).
> >
> > Also:
> >
> > * Most of the "maintainers" would tell you that it is production-ready,
> > but then, they might be biased since most of them are running it in
> > production. YMMV.
> > * It is as poorly documented as most FLOSS projects.
> > * We provide support through the issue tracker, mailing lists, and IRC,
> > and you can purchase support contracts through Riptano.
> >
> >
> > --
> > Eric Evans
> > eevans@rackspace.com
> >
>
>
Re: Cassandra 0.7.0 Release in Riptano public repository?
Posted by Michael Fortin <mi...@m410.us>.
Thanks for your thoughtful and detailed replies Eric, it's much appreciated.
Mike
On Jan 11, 2011, at 11:23 AM, Eric Evans wrote:
> On Tue, 2011-01-11 at 09:23 -0500, Michael Fortin wrote:
>> This my understanding of 0.* releases.
>> - They're not considered production ready by the maintainers
>> - They subject to changes that break backwards compatibility
>> - Generally poorly documented because the api is so volatile
>> - Previous releases are unsupported
>>
>> for 1.* releases
>> - The maintainer is saying this is tested and production ready,
>> sometimes also marked as Final for GA
>> - Minor releases do not break backward compatibility
>> - The major and minor release have some level of support, with open
>> source, that usually means docs and mailing lists but they should be
>> very active.
>> - thoroughly documented
>
> FWIW, your interpretation of what it means to be 1.0, is not wholly
> unique, but it's far from universal either.
>
>> Sorting through the issue tracker is a little to fine grained to get a
>> big picture view of where cassandra is going.
>
> Sorry, I should have been more clear here.
>
> The closest we have to a roadmap are the tickets that are marked as
> blocking the next release, you shouldn't have to do any digging, they're
> all available in one view here:
>
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=12310865&fixfor=12314820
>
> But, it's pretty fluid for the first few months after a new release.
>
>> And, just to be clear, I'm not questioning the maintainers approach,
>> just humbling asking for a little more clarification. Cassandra is
>> awesome, and I'm itching to use it on some production projects where I
>> think it would be a great fit, but 0.* designation scares me a little.
>> Of course, a hastily released 1.* would be worse.
>
> I understand, but what I'm saying is a "1.0" release in this context
> carries special significance that just doesn't map well to open source
> projects. And, in addition to being subjective, your criteria differs
> from that of many people. It might make things easier to just version
> some future release 1.0 and be done with it, but I'd rather be honest
> with you.
>
> This is honest:
>
> * We treated the Google code dump in 2008 as 0.1.0 (though no formal
> release was made).
> * We likewise treated the Apache code dump in 2009 as 0.2.0 (again, no
> formal release).
> * We called the first release under the Apache Incubator 0.3.0.
> * We just now released 0.7.0.
> * We maintain backward compatibility between the "minor" and "revision",
> that is 0.6.1, 0.6.2, 0.6.3, etc.
>
> This is why I said my preference would be to just drop the leading 0.
> We've been using the minor like a major, and the revision like a minor,
> (and we haven't had need for a revision). We've had 7 major releases,
> (5 if you only want to count what's happened under Apache).
>
> Also:
>
> * Most of the "maintainers" would tell you that it is production-ready,
> but then, they might be biased since most of them are running it in
> production. YMMV.
> * It is as poorly documented as most FLOSS projects.
> * We provide support through the issue tracker, mailing lists, and IRC,
> and you can purchase support contracts through Riptano.
>
>
> --
> Eric Evans
> eevans@rackspace.com
>
Re: Cassandra 0.7.0 Release in Riptano public repository?
Posted by Eric Evans <ee...@rackspace.com>.
On Tue, 2011-01-11 at 09:23 -0500, Michael Fortin wrote:
> This my understanding of 0.* releases.
> - They're not considered production ready by the maintainers
> - They subject to changes that break backwards compatibility
> - Generally poorly documented because the api is so volatile
> - Previous releases are unsupported
>
> for 1.* releases
> - The maintainer is saying this is tested and production ready,
> sometimes also marked as Final for GA
> - Minor releases do not break backward compatibility
> - The major and minor release have some level of support, with open
> source, that usually means docs and mailing lists but they should be
> very active.
> - thoroughly documented
FWIW, your interpretation of what it means to be 1.0, is not wholly
unique, but it's far from universal either.
> Sorting through the issue tracker is a little to fine grained to get a
> big picture view of where cassandra is going.
Sorry, I should have been more clear here.
The closest we have to a roadmap are the tickets that are marked as
blocking the next release, you shouldn't have to do any digging, they're
all available in one view here:
https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=12310865&fixfor=12314820
But, it's pretty fluid for the first few months after a new release.
> And, just to be clear, I'm not questioning the maintainers approach,
> just humbling asking for a little more clarification. Cassandra is
> awesome, and I'm itching to use it on some production projects where I
> think it would be a great fit, but 0.* designation scares me a little.
> Of course, a hastily released 1.* would be worse.
I understand, but what I'm saying is a "1.0" release in this context
carries special significance that just doesn't map well to open source
projects. And, in addition to being subjective, your criteria differs
from that of many people. It might make things easier to just version
some future release 1.0 and be done with it, but I'd rather be honest
with you.
This is honest:
* We treated the Google code dump in 2008 as 0.1.0 (though no formal
release was made).
* We likewise treated the Apache code dump in 2009 as 0.2.0 (again, no
formal release).
* We called the first release under the Apache Incubator 0.3.0.
* We just now released 0.7.0.
* We maintain backward compatibility between the "minor" and "revision",
that is 0.6.1, 0.6.2, 0.6.3, etc.
This is why I said my preference would be to just drop the leading 0.
We've been using the minor like a major, and the revision like a minor,
(and we haven't had need for a revision). We've had 7 major releases,
(5 if you only want to count what's happened under Apache).
Also:
* Most of the "maintainers" would tell you that it is production-ready,
but then, they might be biased since most of them are running it in
production. YMMV.
* It is as poorly documented as most FLOSS projects.
* We provide support through the issue tracker, mailing lists, and IRC,
and you can purchase support contracts through Riptano.
--
Eric Evans
eevans@rackspace.com
Re: Cassandra 0.7.0 Release in Riptano public repository?
Posted by Michael Fortin <mi...@m410.us>.
This my understanding of 0.* releases.
- They're not considered production ready by the maintainers
- They subject to changes that break backwards compatibility
- Generally poorly documented because the api is so volatile
- Previous releases are unsupported
for 1.* releases
- The maintainer is saying this is tested and production ready, sometimes also marked as Final for GA
- Minor releases do not break backward compatibility
- The major and minor release have some level of support, with open source, that usually means docs and mailing lists but they should be very active.
- thoroughly documented
Sorting through the issue tracker is a little to fine grained to get a big picture view of where cassandra is going.
And, just to be clear, I'm not questioning the maintainers approach, just humbling asking for a little more clarification. Cassandra is awesome, and I'm itching to use it on some production projects where I think it would be a great fit, but 0.* designation scares me a little. Of course, a hastily released 1.* would be worse.
Mike
On Jan 10, 2011, at 5:22 PM, Eric Evans wrote:
> On Mon, 2011-01-10 at 16:51 -0500, Michael Fortin wrote:
>> Is there a roadmap posted somewhere for cassandra? I didn't see one
>> on the wiki.
>
> The closest we get to a documented roadmap are the bugs that block the
> release in our JIRA instance.
>
>> I was curious to know what major features are in future and if there
>> was a crude timeline for a 1.0 release.
>
> Ugh. The notion of a "1.0" release is an artifact of commercial
> software development, where vendors work behind closed doors to release
> a tightly controlled product on a specific schedule. It makes a lot
> less sense in an open source project where people from different
> companies and backgrounds collaborate using ad-hoc processes, and where
> everything is transparent.
>
> If you ask 10 people what a "1.0" means in the context of Cassandra,
> you're going to see a number of different answers. Some people will
> think It's Time, others that we should have "Gone 1.0" a release or two
> ago, and others still that think we're not yet there.
>
> TL;DR
>
> Your best bet is to evaluate the project for yourself, talk to others
> who've come before, and decide on your own comfort level.
>
> My preference would be to drop the leading 0 (it's never meant
> anything), so 0.7.0 becomes 7.0, the next release 8.0, etc, etc.
>
>
> --
> Eric Evans
> eevans@rackspace.com
>
Re: Cassandra 0.7.0 Release in Riptano public repository?
Posted by Eric Evans <ee...@rackspace.com>.
On Mon, 2011-01-10 at 16:51 -0500, Michael Fortin wrote:
> Is there a roadmap posted somewhere for cassandra? I didn't see one
> on the wiki.
The closest we get to a documented roadmap are the bugs that block the
release in our JIRA instance.
> I was curious to know what major features are in future and if there
> was a crude timeline for a 1.0 release.
Ugh. The notion of a "1.0" release is an artifact of commercial
software development, where vendors work behind closed doors to release
a tightly controlled product on a specific schedule. It makes a lot
less sense in an open source project where people from different
companies and backgrounds collaborate using ad-hoc processes, and where
everything is transparent.
If you ask 10 people what a "1.0" means in the context of Cassandra,
you're going to see a number of different answers. Some people will
think It's Time, others that we should have "Gone 1.0" a release or two
ago, and others still that think we're not yet there.
TL;DR
Your best bet is to evaluate the project for yourself, talk to others
who've come before, and decide on your own comfort level.
My preference would be to drop the leading 0 (it's never meant
anything), so 0.7.0 becomes 7.0, the next release 8.0, etc, etc.
--
Eric Evans
eevans@rackspace.com
Re: Cassandra 0.7.0 Release in Riptano public repository?
Posted by Nate McCall <na...@riptano.com>.
For Cassandra, the issues-to-version is managed daily. Keeping tabs on
that is probably the best idea of a Roadmap. Further, anyone can sign
up for an ASF Jira account and submit issues as well as comment on and
even "vote" for existing ones.
https://issues.apache.org/jira/browse/CASSANDRA
On Mon, Jan 10, 2011 at 3:51 PM, Michael Fortin <mi...@m410.us> wrote:
> Congrats on the release.
>
> Is there a roadmap posted somewhere for cassandra? I didn't see one on the wiki. I was curious to know what major features are in future and if there was a crude timeline for a 1.0 release.
>
> thanks,
> mike
>
> On Jan 10, 2011, at 2:50 PM, Nate McCall wrote:
>
>> The RPM was deployed around 17:00 GMT. Are you trying to download the
>> package directly or was this from yum?
>> http://rpm.riptano.com/EL/6/x86_64/
>>
>> On Mon, Jan 10, 2011 at 1:44 PM, Oleg Tsvinev <ol...@gmail.com> wrote:
>>> Hi,
>>> http://cassandra.apache.org/download/ shows that
>>> "The latest stable release of Apache Cassandra is 0.7.0 (released on
>>> 2011-01-09). If you're just starting out, download this one."
>>> However, I don't see this version in Riptano public repository. The latest
>>> there is still 0.7.0-rc4.
>>> Is there any chance to get it from there?
>>> Thank you,
>>> Oleg
>>>
>
>
Re: Cassandra 0.7.0 Release in Riptano public repository?
Posted by Michael Fortin <mi...@m410.us>.
Congrats on the release.
Is there a roadmap posted somewhere for cassandra? I didn't see one on the wiki. I was curious to know what major features are in future and if there was a crude timeline for a 1.0 release.
thanks,
mike
On Jan 10, 2011, at 2:50 PM, Nate McCall wrote:
> The RPM was deployed around 17:00 GMT. Are you trying to download the
> package directly or was this from yum?
> http://rpm.riptano.com/EL/6/x86_64/
>
> On Mon, Jan 10, 2011 at 1:44 PM, Oleg Tsvinev <ol...@gmail.com> wrote:
>> Hi,
>> http://cassandra.apache.org/download/ shows that
>> "The latest stable release of Apache Cassandra is 0.7.0 (released on
>> 2011-01-09). If you're just starting out, download this one."
>> However, I don't see this version in Riptano public repository. The latest
>> there is still 0.7.0-rc4.
>> Is there any chance to get it from there?
>> Thank you,
>> Oleg
>>
Re: Cassandra 0.7.0 Release in Riptano public repository?
Posted by Nate McCall <na...@riptano.com>.
The RPM was deployed around 17:00 GMT. Are you trying to download the
package directly or was this from yum?
http://rpm.riptano.com/EL/6/x86_64/
On Mon, Jan 10, 2011 at 1:44 PM, Oleg Tsvinev <ol...@gmail.com> wrote:
> Hi,
> http://cassandra.apache.org/download/ shows that
> "The latest stable release of Apache Cassandra is 0.7.0 (released on
> 2011-01-09). If you're just starting out, download this one."
> However, I don't see this version in Riptano public repository. The latest
> there is still 0.7.0-rc4.
> Is there any chance to get it from there?
> Thank you,
> Oleg
>
Re: Cassandra 0.7.0 Release in Riptano public repository?
Posted by Stephen Connolly <st...@gmail.com>.
On 10 January 2011 19:44, Oleg Tsvinev <ol...@gmail.com> wrote:
> Hi,
> http://cassandra.apache.org/download/ shows that
> "The latest stable release of Apache Cassandra is 0.7.0 (released on
> 2011-01-09). If you're just starting out, download this one."
> However, I don't see this version in Riptano public repository. The latest
> there is still 0.7.0-rc4.
> Is there any chance to get it from there?
> Thank you,
> Oleg
>
Just on the off-chance that you are talking about the riptano public
maven repository. The cassandra artifacts from 0.7.0-rc4 are
available from the maven central repository.
-Stephen