> What looks sensible to me would be to implement option one as a "one major > release" feature, during which time an implementation of option two as a > warning rather than an error. > > Then on the next major release crank over to an error, ditch the > work-around, > and everyone wins: you can reject the problems (if I understand option 2 > right) without having to pay the extra cost to check them every time. >
+1 That should not, from what I can see, be significantly harder than option II (which seems to be the current favorite) and greatly reduces its sting. I like. -- Markus ----------------------------------------------------------- The power of accurate observation is commonly called cynicism by those who have not got it. ~George Bernard Shaw ------------------------------------------------------------ -- 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.
