Just a quickie…
I’m seeing Rails 3.2 Beta already on Github, though 3.1 is still at
RC4. Is the plan still to release 3.1 or are we skipping straight to
3.2?
Forgive me if it’s a dumb question: it’s asked honestly.
itsterry wrote in post #1009122:
Just a quickie…
I’m seeing Rails 3.2 Beta already on Github, though 3.1 is still at
RC4. Is the plan still to release 3.1 or are we skipping straight to
3.2?Forgive me if it’s a dumb question: it’s asked honestly.
AFAIK the next public release of Rails will be 3.1. I’m not surprised
they already have a 3.2 branch, because there are already planned
features for 3.2. They need a place to work on those while finishing up
the Rails 3.1 release.
Sent from my iPad
On Jul 5, 2011, at 2:40 AM, itsterry [email protected] wrote:
Just a quickie…
I’m seeing Rails 3.2 Beta already on Github, though 3.1 is still at
RC4. Is the plan still to release 3.1 or are we skipping straight to
3.2?Forgive me if it’s a dumb question: it’s asked honestly.
The Rails core team will always be working on more than one version of
Rails at any given time at different levels of the software pipeline.
For example,
Rails 2.3.x : maintenance only
Rails 3.0.x : mostly maintenance only
Rails 3.1.x : release candidate
Rails 3.2.x : minor release which contains new features and enhancements
In short, they will be always working a future release and it will be
reflected in their respective Github repository. If you’re looking to
build a production Rails application today, I would recommend Rails
3.0.9 or 3.1rc.
Good luck,
-Conrad
Thanks Conrad, that helps.
I’ll use 3.1rc for the production app I’m about to start
Cheers!
Terry
Let me fix this a bit …
Rails 2.3.x : NOT maintained anymore. security or severe bugs only.
branch 2-3-stable.
Rails 3.0.x : Maintenance only. New features are not allowed. branch
3-0-stable.
Rails 3.1.x : Release candidate, feature complete. New features are
not allowed. branch 3-1-stable.
Rails 3.2.x : Future Rails version. New features goes here. branch
master.
Cheers.