On Wed, Apr 20, 2011 at 11:28, Nigel Kersten <[email protected]> wrote:
> http://projects.puppetlabs.com/issues/4938 > I'd quite like to push this through for Statler, but we've already cut > 2.7.0rc1. So, my view is that this sort of thing should be evaluated on a case-by-case basis. Slips happen, and while keeping the RC process pure is good, it shouldn't automatically win over pragmatism and delivering a good product. […] > If we're strict about this, then the above issue shouldn't be > deprecated until Telly, six months from now, and doesn't get removed > until the Release That Is Yet To Be Named a further six months away. > > I'm not particularly happy about that, but I wanted to see what the > community thinks. Is it reasonable for us to target issues like this > at the next 2.7.0 RC? I think, in this specific case, that we should merge the deprecation warning for 2.7.0. Daniel -- ⎋ Puppet Labs Developer – http://puppetlabs.com ✉ Daniel Pittman <[email protected]> ✆ Contact me via gtalk, email, or phone: +1 (877) 575-9775 ♲ Made with 100 percent post-consumer electrons -- 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.
