|
From: | Colin Campbell |
Subject: | Re: Patch meister |
Date: | Thu, 23 Jun 2011 21:31:45 -0600 |
User-agent: | Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110516 Lightning/1.0b2 Thunderbird/3.1.10 |
On 11-06-23 05:38 AM, Graham Percival wrote:
Do either of you have 2-3 hours a week to spend shuffling patches? More directed at Colin than James, but I figured I'd include James in case he was getting sick of doc work and wanted a challenge. I'd like somebody else to be Patch Meister. The most important job is as described under "You can help" on this page: http://percival-music.ca/blog/2011-06-11-lilypond-2.14.html Yes, there's 6 steps. We might need to clarify some of them, but I'm certain that the final list will be less than 12 completely-robotic steps. Another job is to update the Patch-needs_work issues when a new draft is uploaded. I haven't written steps for this, but it would be a similarly robotic step-following process. Cheers, - Graham
I could take it on, Graham. In some ways it's just a bit further and more formal than the "screening" I've been trying to do. I'd suggest a minor edit on your blog though: after the list of steps in "You can help", you might s/need/mind ;>
A related question, though: how do we go about tying issues and patches closer together? It would be extremely valuable either to *require* that anything on reitveld have a formal issue number, even if it's a dev contributing a "hey, look what I wrote" enhancement, or to look for a different platform which combines issue tracking with patch management. As it sits, reitveld doesn't manage projects, only developers, and the issues on code.google.com don't reflect all the issues/patched needing attention. Should we start a GOP discussion, at least to get the views of the developer community on record?
Colin -- The human race has one really effective weapon, and that is laughter. -- Mark Twain
[Prev in Thread] | Current Thread | [Next in Thread] |