On 2007-02-24, at 20:54 , Michael Koziarski wrote: > Generally speaking I track stable, only moving to edge if there's a > big feature I'm after. While we'll always do our best not to bust up > edge too badly, you're kinda crazy if you're using it 'just because' > ;).
I was using trunk before 1.2 because of the long gap since 1.1. Lots and lots of new useful features. I've just switched the app I'm working on back to 1.2.2, for now. I'll keep an eye on ryan's blog and switch to trunk if something cool pops up. Do you think maybe as work on 2.0 progresses, it might be a good idea to maintain a branch to merge stable new features in, along side with a not-so-stable trunk? The purpose would be to provide sort a reliable selection of the more stable features, without actually putting out a release. Or just trunk snapshots (tags) at the most stable revisions. Maybe it's too much work, maybe it'll be useful as a way to garner wider testing for 2.0 features before an RC is out. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
