[zopticity]

Why do we have a post about the release candidate? Is this to raise awareness for the release or something. It doesn't seem to make sense to post about all version. If we did this, Chrome browser would be nuts considering how many versions it goes through!

[steveklabnik]

> It doesn't seem to make sense to post about all version.

2.0.0 is kind of a big deal. It's not just any random version.

Furthermore, projects always have trouble getting people to actually use release candidates. I can't tell you the number of times I've seen a project where two or three RCs get released, issues are fixed, and when final comes out, people complain "omg there's so many bugs." They would have been fixed for final if you'd tried the RC!

[dmethvin]

Preach it brother! The people who don't care about the RC are the ones who jump on it day 1 of the release because it's "finally ready" and then complain about the bugs.

[hartator]

I guess maybe because a release candidate of Ruby might be the "final" Ruby 2.0.0 and it can make gem mainteners want to check their code compatibility. Web developers have difficulties keeping their website up to date with all browser, so it can be overkill to try to keep up with release candidate of every browser.

[taf2]

sure... but ruby is on a yearly release cycle and i don't know about you but this does get me pretty excited. brings out the fan boy in me ;-)

also it gives me heads up that hey new release of ruby coming out soon, maybe i should go test the gems i maintain and make sure they're going to be compatible. RC2 is pretty close to p0

[jewel]

It seems like it'd be possible to automate gem testing for this scenario. Take the 1000 most popular gems, run the tests that come with the gem in 1.9.3. Run the tests again with the RC and see if any that succeed with the stable version fail with the RC.

[steveklabnik]

Many Rubyists use Travis to do CI with their gems, and have ruby-head testing, often with allow-failures set. Here's one of mine: https://travis-ci.org/drapergem/draper

[rrouse]

In theory that would work, but the effort to get all the dependencies working for each gem could be overwhelming.

[jrabone]

It's Ruby. Every little fucking thing is front page news, from drama to RC releases to security holes. Welcome to programming by celebrity, where what you write isn't half so important as what you write it in, and how many tweets it generates.

[pekk]

Because Rails is very popular and serves a particularly vital role in the startup world that HN caters to.

I find this less irritating than constant press release spam from commercial products, at least.

[anko]

you sound bitter.

[TallboyOne]

Quite bitter.