Hi,

As written in GCD 002 “Migrating repositories, issues, and patches to
Codeberg” [1], here we are:

  - Until **December 31st, 2025**, bug reports and patches will be
    accepted both by email (`bug-guix` and `guix-patches`) and on
    Codeberg.
    
  - Soon after **January 1st, 2026**, mailing list administrators will
    set up the `bug-guix` and `guix-patches` mailing lists in “Emergency
    Moderation” mode in the Mailman interface—meaning that messages to
    open *new* issues will not get through anymore.

So let have the month of January as an Advent of Debbugs squashing.  For
the ones of us who are coming to the Guix Days in Brussels, it seems a
good warm up or a way to be actively patient! :-)

And it also seems a good mean for celebrating the coming soon release
v1.5.0! \o/

All in all, I propose to tackle, chase, close and tag the issues
currently tracked by Debbugs:

    https://issues.guix.gnu.org

Well, adding both guix-patches and bug-guix, today I count 3307 open
issues – including 1172 open patches; that’s something!  And we can be
grateful to people (especially Andreas) who already processed many
issues over the past months.

The easy tasks in order to reduce the workload are:

    1. Check the issues you’ve opened:
         comment as still relevant or close it with an explanation.
         any message’s helpful!
         
    2. If you sent a patch, check if it’s still relevant;
         if yes, please consider to open PR instead,
         if no, please close it with an explanation.
       (sorry if your submission has fallen into the cracks)

Two others tasks that help:

    3. For all the patches, check if they’re still relevant;
         if yes, please add a message to say yes, or commit and push it!
         if no, please close it with an explanation.

    4. For bugs,
         a) Comment if you’re able to reproduce.
         b) Ask details if you miss what the bug’s about.
         c) Tag as moreinfo if you’re confident it requires more
            information.
         d) Close it with an explanation if you’re confident the bug had
            been fixed since.

We could have a great party in Brussels if the 1.5.0 is released and the
number of open Debbugs patches becomes half (=586) – although we’ll have
a great party in all the cases. ;-)

1, 2, 3, go!


Cheers,
simon

1: 
https://codeberg.org/guix/guix-consensus-documents/src/commit/9bb95852603d6ea49133ab149c723610aad2f4ff/002-codeberg.md#issue-tracker-migration-path

Reply via email to