[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: gnu-patches back log
From: |
Ricardo Wurmus |
Subject: |
Re: gnu-patches back log |
Date: |
Tue, 07 Mar 2017 13:09:50 +0100 |
User-agent: |
mu4e 0.9.18; emacs 25.1.1 |
Catonano <address@hidden> writes:
> Wrapping up, I think 2 interesting ideas popped up in this thread
>
> One is the automation of building of new packages patches
I wouldn’t know how to set this up. Hydra isn’t powerful enough for our
*current* purposes, so I wouldn’t want to increase the load at this
point.
> Another one is the weekly report about pending patches and merged
>patches
I’d rather not have a weekly report (I get enough email through the
various Guix mailing lists already). The debbugs interface shows all
open patches already. (We should get more people to use guix-patches
instead of guix-devel, though.)
Other than that I’d like to second everything Leo has written.
I agree with Pjotr that obviously it would be nice to have faster/more
reviews/mentoring. That’s something everybody can help with, even if it
is just a matter of reviewing licenses or trying to build or run the
package. But this all falls apart under stress (speaking from
experience here), so it’s best not to force it.
--
Ricardo
GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
https://elephly.net
- Re: gnu-patches back log, (continued)
- Re: gnu-patches back log, ng0, 2017/03/01
- Re: gnu-patches back log, Leo Famulari, 2017/03/01
- Re: gnu-patches back log, Pjotr Prins, 2017/03/01
- Re: gnu-patches back log, Leo Famulari, 2017/03/01
- Re: gnu-patches back log, Pjotr Prins, 2017/03/01
- Re: gnu-patches back log, Catonano, 2017/03/01
- Re: gnu-patches back log,
Ricardo Wurmus <=
- Re: gnu-patches back log, Catonano, 2017/03/13
- Re: gnu-patches back log, John Darrington, 2017/03/01
Re: gnu-patches back log, Ludovic Courtès, 2017/03/06