Issue #1732 has been updated by luke.
This feels like bringing up old, bad blood, but I don't think the process is nearly as haphazard or changing as you make it out to be. The development lifecycle clearly documents how this is supposed to work, and this document has been built over time by the whole community: http://reductivelabs.com/trac/puppet/wiki/DevelopmentLifecycle Prior to git, we were using a process instituted by you: We attached all patches to the tickets. This process, as you and everyone else agreed, was relatively cumbersome, and is part of what led to the adoption of a distributed version control system. Having adopted such a system, we began reassessing the process; you were even included in this reassessment last year. Based on your recommendation, I attempted to find a clean way to use email to manage commits, but I could not consistently apply patches emailed to me, and given that I don't use mboxes, I don't think it was ever going to be clean. After looking around more, we found that encouraging development in branches was a well-established method of solving the same problem, given our much smaller developer base. In looking into it more, we found is that there are multiple clear advantages to encouraging people to work in branches rather than attaching to tickets: * It's easier for the maintainer to manage many patches from many sources * It's easier for the developer to republish new code and for the maintainer to receive updates * It's easier for the maintaner to rebase if necessary * Commit authorship is retained So while, yes, the development lifecycle standards have changed in your development hiatus, they've changed gradually, and with significant feedback from the community. You can even follow some of the changes in the developer calls we've been doing: http://reductivelabs.com/podcast ---------------------------------------- Refactor #1732: Make P::U::Settings a bit thinner http://projects.reductivelabs.com/issues/show/1732 Author: mpalmer Status: Ready for Testing Priority: Normal Assigned to: Category: plumbing Target version: 0.24.7 Affected version: 0.24.6 I've partially refactored the Puppet::Util::Settings class to remove a couple of unused methods, make some other methods private, and remove the direct access to settings via the Puppet module (which according to comments in bug 1683 isn't the way things should be done). ---------------------------------------- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Bugs" 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-bugs?hl=en -~----------~----~----~----~------~----~------~--~---
