Anti-Edge Rails
Rob Funk
But what about maintaining old projects?
Doesn't anyone have to worry about their old Rails 1.2 or even 1.1
projects these days, when the client isn't interested in paying for more
work? ("You finished that already, didn't you? Why should I pay more?")
But is anyone watching for security holes in these old versions?
--
==============================| "A microscope locked in on one point
Rob Funk <rf...@funknet.net> |Never sees what kind of room that it's in"
http://www.funknet.net/rfunk | -- Chris Mars, "Stuck in Rewind"
Rob Biedenharn
I've got Rails projects in production with versions 1.1.6, 1.2.2,
1.2.5, 1.2.6, and 2.0.2
I was on edge for about a week prior to 1.1 because I was doing some
polymorphic associations *manually* and found out that they were in
edge and would be in 1.1. When 1.1 became a release, I left edge.
(And, no, that isn't the project that is 1.1.6, it's the one that
never went to production.)
I've actually considered upgrading the 1.1.6 to 1.2.x several times
when I slammed into doing things the "new" 1.2 way and finding they
don't work in 1.1. (This was before 2.x, of course) This client has
only occasional, minor tweaks at this point so the upgrade would be a
learning, not a billing, opportunity.
If a feature that could be used on a project was only available at a
higher Rails version, I'd find the time to do the upgrade. If there
was a strong enough anti-feature (bug, security flaw, etc.) identified
in the project's old version, that might be a sufficient motivation,
too.
-Rob