On Sat, Jul 16, 2022 at 08:42:39PM +0200, Agostino Sarubbo wrote:
> Hello all,
> I noticed that we have many people that, after received a bug report, ask for 
> what the 
> reported 'qa notice' means.
> Sometimes there is a tracker and people can take an hint from the resolved 
> bugs but 
> when there aren't a lot of info I feel they are a bit lost.

Somewhat orthogonally, it would be a great help to include common
causes, solutions, and reproduction instructions directly in the bug
reports and/or trackers.

> Today, by pure chance, I stumbled upon the "Rust Compiler Error Index" and I 
> thought: 
> why we don't do the same thing with our qa notices?
> I think that devmanual could be the right place and each QA notice should 
> have an 
> 'identification code'.
> In that way we can link the error in the qa notice like:
> https://devmanual.gentoo.org/appendices/qa-notices/qa0001[1]
> https://devmanual.gentoo.org/appendices/qa-notices/qa0002[2]
> and so on.
> Reference: https://doc.rust-lang.org/error-index.html[3]
> What do you think?
> Agostino
> --------
> [1] https://devmanual.gentoo.org/appendices/qa-notices/qa0001
> [2] https://devmanual.gentoo.org/appendices/qa-notices/qa0002
> [3] https://doc.rust-lang.org/error-index.html

Attachment: signature.asc
Description: PGP signature

Reply via email to