How stable is Rails 2.0.2 and 2.1.0 versions

[Satish Kota]

Hi All,

 

I am to start a new project for a client and would like to know if it is fine to build the application on the Rails 2.0.2 or 2.1.0 versions.

 

We always have been having experience in working on ruby 1.8.6 and Rails 1.2.6 versions, so we dont have much experience in how the latest versions behave with old plugins, gems , etc.,

 

Thanks and Regards

Satish N Kota

[Prateek Dayal]

Hi,

I have been using Rails 2.0.2 on www.Muziboo.com for the last few
months. Its been working great so far. No experience with 2.1.0

Regards
Prateek Dayal

--
Prateek Dayal

Startup: http://muziboo.com
Blog: http://prateekdayal.net/blog
Twitter: http://twitter.com/prateekdayal
Flickr: http://flickr.com/photos/prateekdayal

[Satish Kota]

How about AJAX activities and plugins such as authenticated, ferret, taggable, etc., Are they stable as well?

 

Regards

Satish N Kota

 

[Prateek Dayal]

Yeah .. most of the stuff work. Some plugins needed a line or two of
changes that are easily available on a quick google search.

Regards
Prateek

[Nilesh Chaudhari]

The fact that these (2.0.2 & 2.1.0) are tagged versions tells that they are stable. Of course, bugs always exist but for tagged versions, they pretty low in number. In terms of stability, tagged revisions are much better to have than the trunk (edge). 

We recently updated our 2.0.2 app to 2.1 and all tests still pass. I think you should focus on the changes between Rails 2.0 and Rails 1.2.x. That's where you may face most of the issues. As for the plugins/gems, you'll find the updated versions that support 2.x for most popular plugins. 

-Nilesh

[Pratik]

On Wed, Jun 4, 2008 at 10:22 AM, Nilesh Chaudhari <nil...@gmail.com> wrote:
> The fact that these (2.0.2 & 2.1.0) are tagged versions tells that they are
> stable. Of course, bugs always exist but for tagged versions, they pretty
> low in number. In terms of stability, tagged revisions are much better to
> have than the trunk (edge).

IMO, edge is always more stable than any of the tagged versions. Just
lag by a week or so with edge, and you should do just fine. That's
what I tend to do with all my apps. Downside is, if your app depends
on a lot of plugins and you are not interested in hacking those
plugins everytime edge changes an API, you're screwed.

But again, never use plugins without understanding the code.
--
Cheers!
- Pratik
http://m.onkey.org

[Nilesh Chaudhari]

I personally agree with you, Pratik, about edge, though everyone may
not feel comfortable doing that. We too update our applications once
in three weeks to the latest revisions.

We've burnt our fingers with indiscriminate use of plugins. Many small
plugins tend to just hack some base Ruby classes and override their
functionality. In the process, they screw up other parts of the
application. So you should be careful about using plugins. If you want
to use a small plugin, simply open the lib folder of the plugin and
copy only the necessary code to your lib/helpers/tasks folders. Of
course, check the license before you do that.

-Nilesh

[Bhavin Javia]

In addition to rails, plugins etc, always unpack and bundle ALL your gems with your source code.
That will help you avoid a lot of deployment/upgrade issues caused due to version incompatibilities.

- Bhavin

--
-------------------------------------------------
Bhavin Javia,
ThoughtWorks Inc,
Bangalore, India.
Blog: http://www.jroller.com/page/bhavin
YM: javiabhavin

[Jatinder Singh]

> In addition to rails, plugins etc, always unpack and bundle ALL your gems
> with your source code.
> That will help you avoid a lot of deployment/upgrade issues caused due to
> version incompatibilities.

On that note, it may be helpful for ppl to know gem dependency feature
which is baked in to Rails. http://dev.rubyonrails.org/changeset/9140

Jatinder