Making a new project, should I choose rails 2.3.5 or 3.0 .0 beta?

Rails
1

hey,
I am making a new project, and I’ve been having trouble deciding
between rails and 3.5 and rails 3.0.0 beta one. I realize that rails
3.0.0 should be out of beta sometime mid-summer, which is around the
time I expect to launch a project. I try to think ahead, and in many
ways it makes sense to program and 3.0 .0. Yet the language is full
of bugs still. So should I launch with 2.3.5 instead?I could really
use your feedback and appreciate any opinions and comments.

Thank you,
Ryan

2

On Sun, Feb 14, 2010 at 10:43 PM, princezuda [email protected] wrote:

Thank you,
Ryan

Ryan, you can start development now using Rails 2.3.5 and Ruby 1.9.1
today.
Then
when you’re ready to make the leap to Rails 3.0, you can simply make a
Rails
3.0 branch of your web application. However, in the meantime, I would
recommend
following the Rails 3.0 threads, release notes, and blogs posts to
remain
current.

Good luck,

-Conrad

3

I just had to make a similar decision. In order to get something going
quickly I stuck with 2.3.5. Rails 3 seems great, but most of the
plugins I
tried had issues so I decided to wait.

-ben

4

On Mon, Feb 15, 2010 at 9:17 AM, ben wiseley [email protected] wrote:

I just had to make a similar decision. In order to get something going
quickly I stuck with 2.3.5. Rails 3 seems great, but most of the plugins I
tried had issues so I decided to wait.

-ben

Ben, did you file tickets against each of the plugins and gems that
didn’t
work with Rails 3.0? Also, I would recommend updating the following
site:

http://www.railsplugins.org

-Conrad

5

On Mon, Feb 15, 2010 at 11:59 AM, ben wiseley [email protected]
wrote:

No - I didn’t. I didn’t realize we were supposed to do that but I’ll
start. Sorry about that. I just figured that was a “plugins need to be
updated” issue and not a Rails 3 issue.

-ben

Ben, it’s simply recommendation so that things can get resolved sooner
rather than later.

-Conrad

6

No - I didn’t. I didn’t realize we were supposed to do that but I’ll
start.
Sorry about that. I just figured that was a “plugins need to be
updated”
issue and not a Rails 3 issue.

-ben