On Wed, May 25, 2011 at 5:17 PM, Aaron Patterson
<aaron / tenderlovemaking.com> wrote:
> ZOMG HI EVERYBODY!!!! =A0HAPPY WEDNESDAY (UTC-7).
>
> I am EXCITED, PLEASED, and even MORE EXCITED to announce the release of t=
he
> Rails 3.0.8 released candidate NUMBER ONE!
>
> ## OMG RELEASE CANDIDATE. =A0WHAT DOES IT MEAN?
>
> This is a release candidate! =A0It means that we (the rails core team) ar=
e asking
> *you* (our lovely users) to test out the code that we'd like to release!
>
> This is your chance to VETO our release of Rails 3.0.8 final!
>
> ## VETO?? =A0WHY WOULD I DO THAT?
>
> Well you see, dear public, let me explain. =A0In order to bring you this =
latest
> and greatest released of rails, we've made bug fixes and changed codes.
> Unfortunately, that means that we may have inadvertently broken your
> application. =A0We don't want to break your application, we want to fix b=
ugs!
>
> This is your chance to try our the release candidate and let us know if w=
e've
> broken your application!
>
> ## HOW DO I TEST OUR YOUR WONDERFUL AND AMAZING RELEASE CANDIDATE?
>
> Very simple! =A0If you're using bundler, just update your Gemfile to poin=
t at
> rails version '3.0.8.rc1'. =A0Then do a `bundle update`, and you're off t=
o the
> races! =A0Make sure your application behaves normally, all your tests pas=
s, etc.
>
> ## I think I've found a boog! =A0How do I veto???
>
> It's easy, breezy, beautiful, to veto! =A0Just reply to this on the [rail=
s-core
> mailing list](http://groups.google.com/group/rubyonrails-core?pli=3D1), a=
nd let us
> know what went wrong! =A0We'll fix the problem and cut another release ca=
ndidate.
>
> Make sure to check that your failure does not occur on Rails 3.0.7, but *=
does*
> occur on the release candidate. =A0If the failure is also on 3.0.7, we st=
ill want
> to know! =A0It just won't block our release.
>
> ## TELLME THE CHANGES YOU'VE MADE!
>
> Ok, just calm down. =A0For now, go check out this link on github:
>
> =A0https://github.com/rails/rails/compare/v3.0.7...v3.0.8.rc1
>
> Or go check out the CHANGELOG files in each project. =A0When we release t=
he final,
> I'll add the changelog to the announce email.
>
> ## WHEN WILL THE FINAL RELEASE BE??? =A0TELL ME NOW!!!
>
> Typically we release the final version 72 hours after the release candida=
te.
> But this weekend is a holiday, so I don't feel like doing a release this
> weekend. =A0Instead, I will target the final to be released on March 31st=
.

FFFFFFFUUUUUUUUUUUUUUUUUUUUUUUUUUUUU

Did I say "March"?  I meant "May".

Despite my excited tone, I *may* actually be dead tired.

--=20
Aaron Patterson
http://tenderlovemaking.com/