Hello, On 10 January 2013 21:51, Eluze <elu...@gmail.com> wrote:
> David Kastrup wrote > > Eluze < > > > eluzew@ > > > > writes: > > > >> as to the backfilling I need to know more about what this means exactly! > > > > Take over. Put issues with a patch for which the review indicates no > > further need for discussion on a countdown, and announce them. When a > > countdown is finished without significant protests, put the issue on > > push status and announce that. > > Take over. > ??? > > probably I should have a look at the contributor's guide to see see what is > there: > > - how do I know there is a patch for an issue and no further need for > discussion (can I get this information from the issue tracker or do I need > other sources?) > Rietveld Issue (linked in the tracker) Tracker itself Colin says he scans all the email lists too (although I personally wouldn't scan 'user' - only because there are already a lot of places to check if you include bug and dev) Anything more is just going beyond what is expected. There are often enough eyes on things to catch patches that shouldn't be pushed but have been set as such because no one comments. It seems that some devs like to put a LGTM whereas others just flag problems when there is one a sort of 'new news is good news approach'. Some parts of the code only one or two can probably comment on anyway/ > - what does _put_the_issue_on_push_status_ mean exactly > It means you find the issue on the trackjer and chang its status from Patch-Review, to Patch-Countdown then to Patch-push. So it sounds like you spend a lot of time in the tracker. :) > > I will see in the next few days what information I can gather from CG or > the > Google issue tracker > There may not be anything useful at this time - I haven't checked but Colin said he would update the CG guide with this information (or at least what he does) before he finishes this weekend. regards James _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
