On Nov 28, 2007, at 12:59 AM, Michael Sheets wrote:
On Nov 27, 2007, at 5:33 PM, Duane Johnson wrote:
Change rhtml defaults to html.erb [thanks to Nic Williams]
I'll presume this is a Rails 2.0 change… Anyone have any good ideas
on how to handle Rails 2? Likely some stuff will be specific like
this; but some people will be on Rails 1 for a while before they
update their apps. Should we freeze out a copy for Rails 1 and
continue updating the main one or?
Don't use rails anymore so mainly trying to get people talking
about it here, I don't know how fast adoption is going, how many
changes are needed, etc.
Perhaps the best thing to do would be to have an environment variable
that we check for the user's version preference? I imagine that
developers will (potentially) work on new apps with Rails 2.0 as well
as maintain old 1.0 apps. Just because Rails 2.0 becomes the
standard doesn't mean all old apps become "untouchable" :)
The trouble with this, of course, would be maintenance. I'm not sure
if I have the time to do a proper job of this. Any other ideas or
offers are welcome.
Duane Johnson
_______________________________________________
textmate-dev mailing list
[email protected]
http://lists.macromates.com/mailman/listinfo/textmate-dev
