On Thu, Jul 22, 2010 at 12:21 PM, Marnen Laibow-Koser <[email protected]> wrote: > Jeremy Kemper wrote: >> On Thu, Jul 22, 2010 at 11:40 AM, Marnen Laibow-Koser >> <[email protected]> wrote: >>> and it's now 24 July, I don't think it's inappropriate to get impatient >>> for a release or an explanation of the delay. �Heck, if they asked for >>> help, they might get some, but this silence is bad if the core team want >>> to keep their credibility. �Why should I trust a core team that can't >>> get its act together to take 2 minutes to write a blog post explaining >>> why the release was delayed? >> >> This should help clear things up: http://bit.ly/diXfGx > > Oh, that was classy from a member of the core team. Not. > > That attitude could get me (and probably a lot of others) to quit using > Rails. And I'm a Rabid Rails Fanboy [TM].
An attitude of entitlement just rubs everyone wrong and doesn't move the project forward. Your annoyance is understandable but, alone, it is not constructive. Ultimately, your message is spot-on. It has been a while and many are on pins and needles waiting for a non-beta gem to munch on. Real soon now. We, too, are pretty annoyed that the release candidate has dragged on, but we want a candidate we'd feel comfortable deploying to production with our own apps. Thankfully, we've had tons of people testing the betas and bringing the polish up to release quality. That means a short RC cycle. Check out http://github.com/rails/rails/compare/v3.0.0.beta4...master for a sense of the work that has been going into this. This release is going to rock. jeremy -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
