Backporting patches here and there to the last stable is getting to be a pain. My hunch is that since Rails hasn't crystallized yet, you *need* to be tracking svn to make applying patches as easy as possible (to keep typo usable as Rails shifts underfoot).
Trunk rails sounds like a bad idea to me for production, as you'd be chasing a moving target on a daily basis. I'm planning to keep 'gem update'ing rails releases [ I don't have much choice as textdrive bump rails for me :) ]and pulling bits of trunk svn when I need to. On 02/11/05, Rob Sanheim <rsanheim at gmail.com> wrote: > Hi folks, > I'm thinking of spending some time getting trunk rails + latest typo > from svn working on a dev box and then "in production". Are things > generally stable enough that I could do this without too much pain, or > should I wait it out a bit more as Rails 1.0 lands? > thanks, > Rob > -- > http://www.robsanheim.com/ > > _______________________________________________ > Typo-list mailing list > Typo-list at rubyforge.org > http://rubyforge.org/mailman/listinfo/typo-list > -- Rasputin :: Jack of All Trades - Master of Nuns http://number9.hellooperator.net/
