Rails - Feb 2005 - locking to a version by default

Has anyone considered making Rails "lock" to specific version numbers 
by default (rather than require the developer to manually do it for 
each new project)?

It seems to me to be something that any half-smart developer would want 
to do (rather than be surprised when the next gem breaks stuff), and so 
far, it''s something that the developer has to "remember". 
Given all
the automation and help that Rails has built in, this seems like an 
oversight.

I''d like to think that when I type `rails mynewproject` it would 
generate the appropriate "lock version" lines environment.rb based on 
the current version of gem used.

---
Justin French, Indent.com.au
justin.french-zULN+VWqVOIpAS55Wn97og@public.gmane.org
Web Application Development & Graphic Design

> I''d like to think that when I type `rails mynewproject` it would 
> generate the appropriate "lock version" lines environment.rb
based on
> the current version of gem used.
I would not like that as I would have to update this every time I get 
new beta gems.

What I WOULD like, though, is "rake lock_gems" that would do that for 
me based on the current gems. That would be really sweet. Then I would 
be able to lock when I''m done staying at the edge.
--
David Heinemeier Hansson,
http://www.basecamphq.com/   -- Web-based Project Management
http://www.rubyonrails.org/  -- Web-application framework for Ruby
http://www.loudthinking.com/ -- Broadcasting Brain