

Subject: [ANN] Rails 3.0.6.rc1

From: Aaron Patterson <aaron@ n r v a n c >

Date: Wed, 30 Mar 2011 06:07:33 +0900

--EVF5PPMfhYS0aIcm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable ZOMG HAPPY TUESDAY (UTC-7)!!! <3<3<3<3<3 I am happy to announce that the first release candidate for Rails 3.0.6 has been pushed to rubygems.org. ## Release Candidate: What does it mean? The release candidate is very similar to what we will actually release for version 3.0.6. The reason that we release an RC is so that the community c= an have a chance to postpone or veto commits that have happened between the previous version and the version we're about to release. We are asking you (yes you!) to *try out* the release candidate. If someth= ing that changed between 3.0.5 and this release candidate breaks your applicati= on, we want to know about it! ## How do I try it out? Simply update your Gemfile to point at the rails version "3.0.6.rc1", then `bundle install`. ## Where can I see a list of Changes? Either look at the CHANGELOG in each particular project on [github](https://github.com/rails/rails/tree/3-0-6), *or* check out the handy [compare view](https://github.com/rails/rails/compare/v3.0.5...v3.0.6.rc1). Again, per project changelogs: https://github.com/rails/rails/tree/3-0-6 *or* compare view: https://github.com/rails/rails/compare/v3.0.5...v3.0.6.rc1 ## ZOMG SOMETHING BROKE, WHAT DO I DO? Email the [rails core mailing list](http://groups.google.com/group/rubyonra= ils-core) at let us know about the problem! We will discuss the problem and how to h= andle it before the final version is pushed. ## WHEN WILL THE FINAL VERSION BE RELEASED?!?!?! Unless there are problems found in the RC, we will release the final version no less than 72 hours from *now*, but not exactly 72 hours from now (as I w= ill be on vacation :-P). If there are problems found in the RC, we will release another RC and give = the community another chance to test before releasing. ## IN CLOSING Remember, this is *your* chance to veto / postpone our release. Despite the lols I have in this email, please take advantage of this opportunity! We d= o not want to break people's applications. The best we can do is ask for help! Thanks for listening everyone! <3 <3 <3 <3 <3 --=20 Aaron Patterson http://tenderlovemaking.com/ --EVF5PPMfhYS0aIcm Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (Darwin) iQEcBAEBAgAGBQJNkknmAAoJEJUxcLy0/6/Gz4UH/2kJBv8BAVougqdO4Qx+svtg 3KYYQ57UjmjRwIP3CFAo9oxBtxhdNekHphqRmiHm/LVbalgyFXBVzjIYX0EOzFh3 RF3FRCA254Ao13iA+96NELVIe/EoQ/H1LoYS8OwZuqvUOllJuVo7UKVaOJgBEC2E tJtp0meVl9nXIUlvvVeHXlS3TSgbyzkyPuIWO0z0CRi2TY9VZW+d7ZGHLuynazjF YexXGvhiLsn6ae0v/0oFz8L6+o8RA2HxbmG7kYaJVPg2+bfciYgqziFfIEYIk8Sy VqT9dVTv0Rz/1IS2cpILKcKEzyQhGW0RUUYdWv/T49Yp4zTFGVMBn5QeQKfR500= =vdf+ -----END PGP SIGNATURE----- --EVF5PPMfhYS0aIcm-- ZOMG HAPPY TUESDAY (UTC-7)!!! <3<3<3<3<3 I am happy to announce that the first release candidate for Rails 3.0.6 has been pushed to rubygems.org. ## Release Candidate: What does it mean? The release candidate is very similar to what we will actually release for version 3.0.6. The reason that we release an RC is so that the community c= an have a chance to postpone or veto commits that have happened between the previous version and the version we're about to release. We are asking you (yes you!) to *try out* the release candidate. If someth= ing that changed between 3.0.5 and this release candidate breaks your applicati= on, we want to know about it! ## How do I try it out? Simply update your Gemfile to point at the rails version "3.0.6.rc1", then `bundle install`. ## Where can I see a list of Changes? Either look at the CHANGELOG in each particular project on [github](https://github.com/rails/rails/tree/3-0-6), *or* check out the handy [compare view](https://github.com/rails/rails/compare/v3.0.5...v3.0.6.rc1). Again, per project changelogs: https://github.com/rails/rails/tree/3-0-6 *or* compare view: https://github.com/rails/rails/compare/v3.0.5...v3.0.6.rc1 ## ZOMG SOMETHING BROKE, WHAT DO I DO? Email the [rails core mailing list](http://groups.google.com/group/rubyonra= ils-core) at let us know about the problem! We will discuss the problem and how to h= andle it before the final version is pushed. ## WHEN WILL THE FINAL VERSION BE RELEASED?!?!?! Unless there are problems found in the RC, we will release the final version no less than 72 hours from *now*, but not exactly 72 hours from now (as I w= ill be on vacation :-P). If there are problems found in the RC, we will release another RC and give = the community another chance to test before releasing. ## IN CLOSING Remember, this is *your* chance to veto / postpone our release. Despite the lols I have in this email, please take advantage of this opportunity! We d= o not want to break people's applications. The best we can do is ask for help! Thanks for listening everyone! <3 <3 <3 <3 <3 --=20 Aaron Patterson http://tenderlovemaking.com/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (Darwin) iQEcBAEBAgAGBQJNkknmAAoJEJUxcLy0/6/Gz4UH/2kJBv8BAVougqdO4Qx+svtg 3KYYQ57UjmjRwIP3CFAo9oxBtxhdNekHphqRmiHm/LVbalgyFXBVzjIYX0EOzFh3 RF3FRCA254Ao13iA+96NELVIe/EoQ/H1LoYS8OwZuqvUOllJuVo7UKVaOJgBEC2E tJtp0meVl9nXIUlvvVeHXlS3TSgbyzkyPuIWO0z0CRi2TY9VZW+d7ZGHLuynazjF YexXGvhiLsn6ae0v/0oFz8L6+o8RA2HxbmG7kYaJVPg2+bfciYgqziFfIEYIk8Sy VqT9dVTv0Rz/1IS2cpILKcKEzyQhGW0RUUYdWv/T49Yp4zTFGVMBn5QeQKfR500= =vdf+ -----END PGP SIGNATURE-----