Bug #3426
Package updates on the mailing list
Status:
not-a-bug
Priority:
bug
Assignee:
-
% Done:
50%
Description
Just to make it easier to track, I'm linking to all the different package updates on the mailing list that I sent:
- Inspircd: https://lists.parabola.nu/pipermail/dev/2023-January/008421.html
- Thinkfan: https://lists.parabola.nu/pipermail/dev/2023-January/008423.html
- Lagrange: https://lists.parabola.nu/pipermail/dev/2023-January/008431.html
- phc-intel: https://lists.parabola.nu/pipermail/dev/2023-January/008433.html
- GNU Rush: https://lists.parabola.nu/pipermail/dev/2023-January/008434.html
- terminal-colors, memlockd, musecore: https://lists.parabola.nu/pipermail/dev/2023-January/008438.html
Related issues
History
Updated by bill-auger over 1 year ago
lumping multiple concerns into the same ticket, doesnt improve
track-ability (as a bug tracker normally would) - the email
thread subjects are enough to allow people to follow each
to make them more trackable in the conventional sense, you could
open pull requests on pagure (one per package) - a forge
automatically organizes those, presents them in a uniform way,
and makes them easily trackable
all activity (state changes, comments, etc) are posted to the
mailing list - interested "watchers" may choose to track those
pull requests, either via the pagure interface, or via the
mailing list
Updated by bill-auger about 1 year ago
- Related to Feature Request #3393: delete 'Packaging Rrequest' as valid redmine 'Issue Concern' (aka: Tracker) added