Rails 2.0

Rails
1

using rails 1.2.6, is it worth switching to 2.0 now ?

2

using rails 1.2.6, is it worth switching to 2.0 now ?

By “using” do you mean a site in production? Or a site just beginning
development? Or your personal blog? How important is uptime? How much
time do you have to find any problems (in your code and in your
plugins)?
How much do you care? Why do you want to switch?

If it were me and it was a production site I cared about and I didn’t
need
something in 2.0 I would leave it alone until 2.0.1 comes out. Or
something close to that.

  • 2 cents.

-philip

3

Philip H. pisze:

  • 2 cents.

-philip

its personal site, just for fun, i just wonder if hdd says that 2.0 is
not revolutionary, maybe it isnt worth it.

4

Philip H. wrote:

using rails 1.2.6, is it worth switching to 2.0 now ?

By “using” do you mean a site in production? Or a site just beginning
development? Or your personal blog? How important is uptime? How much
time do you have to find any problems (in your code and in your
plugins)?
How much do you care? Why do you want to switch?

If it were me and it was a production site I cared about and I didn’t
need
something in 2.0 I would leave it alone until 2.0.1 comes out. Or
something close to that.

  • 2 cents.

-philip

i am with philip.

if you notice in the 2.0 release notes, there are notes for ruby to help
you change your code to remove depreciated code. then you have to worry
your server works. i would let the bleeding edge developers, come back
from the hospital, before you jump in there. you have to be sure your
server works/supports 2.0. that is a big deal.

CAN a server have multiple versions of ruby, and also rails, installed.

where is that fred guy?

5

I’d start it on the 2.0 RC if it’s a personal site but for no
particular reason other than I absolutely love some of the
improvements!

6

On Dec 2, 2007 2:29 PM, Trent B. [email protected]
wrote:

need
you change your code to remove depreciated code. then you have to worry
your server works. i would let the bleeding edge developers, come back
from the hospital, before you jump in there. you have to be sure your
server works/supports 2.0. that is a big deal.

CAN a server have multiple versions of ruby, and also rails, installed.

Absolutely, it’s not all that hard to compile multiple versions of ruby
so
that they co-exist on a single server, and gem makes it very easy to
have
multiple versions of rails installed. Managing which versions you’re
using
in what place can be fiddly but also isn’t very hard.

That said, when deploying to production it is best to freeze rails into
your
application. That way you know you can upgrade the version of rails
you’re
running on your own schedule.

If you have good test coverage then upgrading to a new version should be
pretty easy and safe. Simply update the version of rails you have in
your
vendor folder, run your tests and fix any issues that come up. I’d have
no
qualms about updating an app with a good test suite to rails 2.0, and
regularly deploy apps based on versions of rails pretty close to Edge.

James.

–
James S. - Web D.
Work : Processing Greenbelt 2009 – James Stewart
Play : http://james.anthropiccollective.org