From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: December 2020 (old) bugs squashing!
Date: Sun, 10 Jan 2021 22:06:26 -0500 [thread overview]
Message-ID: <877dok41fx.fsf@gmail.com> (raw)
In-Reply-To: <86pn3tv5ag.fsf@gmail.com> (zimoun's message of "Tue, 01 Dec 2020 17:51:03 +0100")
Hi Simon,
zimoun <zimon.toutoune@gmail.com> writes:
> Hi,
>
> Let’s have an Advent calendar effort! Everybody out there who is not
> familiar with this tradition of an « Advent calendar » and to avoid any
> ambiguity, I am appropriating myself the concept*: all of us try to
> close one or more bug per day from 1rst to 31th December, then 2021 will
> start on new balls as in tennis match. :-)
>
> In priority let pick bugs older than #30000 (~Jan. 2018).
>
> <http://issues.guix.gnu.org/forgotten>
>
> From Debbugs, I count 151 bugs or forgotten patches, almost 3 years!
> Time to close them or investigate more.
>
>
> If you do not know how to proceed:
>
> 1. pick an old bug and read the thread
> 2. if the last message is ending with an unanswered question, then mark
> it as moreinfo: send an email to control@debbugs.gnu.org using the
> bug number (e.g., 23456) with:
>
> tags 23456 moreinfo
> thanks
>
> Please give a look at:
> <https://debbugs.gnu.org/server-control.html>
>
> 3. if you do not know what to do, then reply by asking if the bug is
> still relevant for the author. Please provide one line to remember
> the topic and the link which points to the bug:
>
> <http://issues.guix.gnu.org/issue/23456>
>
> 4. if it is a patch, then check if it is not superseded by something
> already merged, else try to apply it and report success, rebase or
> failure.
>
> Last, good candidates are bugs with only one or two messages.
>
>
> I hereby offer some ’(define drink)’ for the one who will close as many
> issues as possible in those 31 days. Well, with the hope to meet those
> bug fighters once real time meeting will be possible again, otherwise
> you will win my gratitude. :-)
>
> For now, Tobias and Maxim have good score but hey we are only the 1th
> day. ;-)
Eh, 2020 is behind us and I don't think I managed to close much bugs in
last December; it's a priority I'll try to keep up with in 2021. Let's
bring the number of issues down to something we can fit in our head more
easily!
Thanks for the initiative :-).
Maxim
next prev parent reply other threads:[~2021-01-11 3:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-01 16:51 December 2020 (old) bugs squashing! zimoun
2020-12-05 15:26 ` Ludovic Courtès
2020-12-22 17:31 ` zimoun
2020-12-05 17:42 ` Bonface M. K.
2020-12-06 0:34 ` Ricardo Wurmus
2020-12-06 15:06 ` Bonface M. K.
2020-12-07 2:26 ` zimoun
2020-12-07 10:59 ` Bonface M. K.
2021-01-11 3:06 ` Maxim Cournoyer [this message]
2021-01-11 14:00 ` zimoun
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877dok41fx.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=guix-devel@gnu.org \
--cc=zimon.toutoune@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).