Luke Kanies wrote: > On Oct 27, 2010, at 1:54 PM, Jeff McCune wrote: > >> On Wed, Oct 27, 2010 at 4:49 PM, Thomas S Hatch <[email protected]> wrote: >>> If it is moved off list, please maintain a public list where we can continue >>> to receive these posts. >> +1 for maintaining a public list. I personally find it very useful. >> >> I also think there should just be one list for code review and >> patches. It's going to be confusing and possibly create information >> sinkholes if community patches go to puppet-dev but puppet-labs >> developer patches go somewhere else. > > This seems like a good middle-ground. We could repurpose the existing > puppet-commits list, or (of course) make a new one.
So my concern here is the potential for confusion between what's reviewed/is/isn't/etc. Already we have issues where patches slip through the cracks - both internal and community patches. If we set-up up a different list it should ONLY be if we've built a more robust review process. James -- Puppet Labs - http://www.puppetlabs.com C: 503-734-8571 -- 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.
