[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
gnu-patches back log
From: |
Pjotr Prins |
Subject: |
gnu-patches back log |
Date: |
Tue, 28 Feb 2017 06:25:31 +0000 |
User-agent: |
Mutt/1.6.2 (2016-07-01) |
Now we have debbugs we can see there is a building back-log:
https://debbugs.gnu.org/cgi/pkgreport.cgi?package=guix-patches;max-bugs=100;base-order=1;bug-rev=1
A patch like this one
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=25725
has been two weeks without comment. I think we should not leave patches without
feedback longer than one week - even 3 days, to be honest. It is the surest way
to kill enthusiasm.
To move forward with Guix and to recognise the effort new submitters
put in I would like to ask *all* reviewers to pick an outstanding
patch on a regular basis. If reviewers split the work it should be doable.
Would it be an idea to send out weekly E-mails with patches that had
no attention to a select list of reviewers? Or maybe to the ML as a
whole? Basically it would read:
Summary
Status
31 Outstanding
18 Resolved
Severity
49 Normal bugs
Classification
22 Patch Available
9 Unclassified
Patches older than 1 week:
gnu: mumble: Build with 'murmur' server component. Modified 13 days ago;
gnu: Add blists. Modified 13 days ago;
gnu: Add lush2. Modified 13 days ago;
etc.
Pj.