> 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?
We definitely don't want to have such a long gap between releases
again, to this end we've already done a few things differently. Most
importantly point releases have included low-impact new features like
:conditions=>{:foo=>1..5} and map.resource.
We'll keep that up.
Once 2.0 is feature complete, we should also push more beta gems, to
make it easier to test. However maintaining yet-another-branch is
probably just as much work as stablising for a release. If a feature
can be easily back ported to 1.2.x, then we should probably just do
that.
--
Cheers
Koz
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
