On Sep 14, 2010, at 9:24, James Turnbull <[email protected]> wrote:
Luke Kanies wrote: On Sep 14, 2010, at 7:40, Brice Figureau <[email protected]> <[email protected]> wrote: On Tue, 2010-09-14 at 07:19 -0700, Luke Kanies wrote: What's the reason for this change? I think it's for rails 3 support. Correct - people with ActiveRecord 3.0 were failing the detection. Ah. How will people be treated when running incompatible versions,given howmoften that happens with Rails? At the moment the only constraint we're aware or is "ActiveRecord prior to 2.1" doesn't work. So we'll cross the bridge when someone finds an incompatible version? I don't see an easy way of doing otherwise to detect a current unknown? I'm not saying I see an easy way to detect compatibility, just that because Puppet and Rails releases aren't syncronized we saw a lot of user confusion when attempts at using incompatible versions failed in weird ways. Like with rspec, we decided that the only reasonable solution wad to declare fixed version support. I'm not saying this is necessarily a bad choice, but it will almost definitely incur a higher support cost overall. -- Luke Kanies | +1-615-594-8199 -- You received this message because you are subscribed to the Google Groups "Puppet Developers" 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/puppet-dev?hl=en.
