On Thu, May 22, 2025 at 11:36:50AM +0300, Hakan Bayındır wrote:
I also like bugreport, debbugs, and current workflow, and it follows natural to me (considering I'm both experienced with Debian ecosystem and nearing graybeard territory). However, the initial experience is a bit disconcerting for the newcomers, and the younger developers want a bit snappier experience from my experience, mostly faster mail processing.
Older developers, especially ones that don't just work on bugs in their own packages, also want faster mail processing...
As a side note, as I just looked to the documentation (the links at [0]), there's no any examples of a complete mail message for manipulating bugs in the BTS docs. Yes, the reference is there, but seeing an example of how a complete mail message looks for manipulating a bug report will be very helpful for the newcomers and folks who use BTS occasionally. IOW, the man pages are missing an "EXAMPLES" section.[0]: https://www.debian.org/Bugs/
I'd say that these 6 linked pages should be burned down and rebuilt from scratch but that's likely too controversial and I won't volunteer for that anyway. All these years I need to click through all of them every time to find what I need, and more recently I use the bts(1) manpage instead, where applicable, hoping that the semantics are sufficiently similar to the control@ ones.
-- WBR, wRAR
signature.asc
Description: PGP signature
