On Feb 10, 2010, at 12:25 AM, Brice Figureau wrote:
On Tue, 2010-02-09 at 17:15 -0800, Markus Roberts wrote:
[...]
* If you have code that ought to be in the testing branch:
* Make sure it's listed on a ticket
* Make sure the ticket is marked ready for testing
* If it depends on any other branches, make sure to note that fact
* Track the ticket for changes; questions, status changes (e.g. to
"code insufficient" if it causes merge conflicts) and
links to the tickets for any bugs discovered in the testing
process.
Hmm, does that mean you'd accept any patch as being part of "testing",
if the only thing we need to do is log a ticket and change its
status to
ready for testing?
I mean for instance my puppetd streaming patch has low chance (in its
current state) to get accepted and merged, will it enter testing
without
any more proof-reading if I just log a ready for testing ticket?
This would generally be my preference, roughly - the barrier of entry
for code making it into the testing branch should be pretty minimal,
while allowing us to make the barrier for getting into master
considerably higher.
[...]
--
Take the utmost trouble to find the right thing to say, and then say
it with the utmost levity. -- George Bernard Shaw
---------------------------------------------------------------------
Luke Kanies -|- http://reductivelabs.com -|- +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.
