From: Thorsten Leemhuis <firstname.lastname@example.org> To: ksummit <email@example.com>, Greg KH <firstname.lastname@example.org>, Sasha Levin <email@example.com> Cc: Linux Kernel Mailing List <firstname.lastname@example.org>, email@example.com Subject: [Ksummit-discuss] FYI & RFC: obsoleting reporting-bugs and making reporting-issues official Date: Fri, 26 Mar 2021 07:13:09 +0100 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) Lo! Since a few months mainline in Documentation/admin-guide/reporting-issues.rst contains a text written to obsolete the good old reporting-bugs text. For now, the new document still contains a warning at the top that basically says "this is WIP". But I'd like to remove that warning and delete reporting-bugs.rst in the next merge window to make reporting-issues.rst fully official. With this mail I want to give everyone a chance to take a look at the text and speak up if you don't want me to move ahead for now. For easier review I'll post the text of reporting-issues.rst in reply to this mail. I'll do that in a few chunks, as if this was a cover letter for a patch-set. Note, the version I'll send in some areas looks a bit different from the one currently in mainline. That's because the text I'll send already incorporates a few patches from docs-next that are waiting for the next merge window; I also removed the "WIP" box as well as two remaining "FIXME" notes, as those point to aspects I mention below already. @Greg, @Sasha, I'd be especially glad if at least one of you two could take a look and yell if there is something you really dislike from the perspective of the stable maintainers. @Everyone: if you provide feedback, please state if you think something needs to be fixed before I remove the WIP box. Everything else I might leave for later depending on how much feedback I get and how much time I can find to work on it before the next merge window opens. It's pretty obvious reporting-issues in a lot of way is quite different from reporting-bugs, so describing the differences would be hard and likely not worth it. But there are a few things hidden in the details I'd like to bring attention to, to ensure they are fine for everyone: - the old text (reporting-bugs.rst) took a totally different approach to bugzilla.kernel.org, as it mentions it as the place to file issue for people that don't known how to contact the appropriate people; the new text (reporting-issues) explains how to decode the MAINTAINERS file and mentions out bugtracker rarely, because it isn't working that well (but nevertheless is useful); those places that mentions it explain that it's often the wrong place to report an issue. - the new text tells users to always CC LKML on reports - the new text tells people pretty directly (and early on!) they will have to install a vanilla mainline kernel along the way (stable is mentioned as an option, longterm discouraged); but it also states some maintainers are willing to accept reports from distro kernels as long as they are quite close to vanilla mainline or stable. - the text doesn't yet mention the new 'linux-regressions' mailing list that was basically agreed on a few days ago (https://lore.kernel.org/lkml/CAHk-=wgiYqqLzsb9-UpfH+=ktk7ra-2fOsdc_ZJ7WF47wS73CA@mail.gmail.com/ ), as I haven't asked yet for its creation. Will do so soon. Hope that's okay for everybody. Ohh, and I hope it was okay to CC ksummit-discuss, as that's afaics the best way to reach all the important people and maintainers (sometimes I wonder if we should have a better list for this). And it's IMHO on topic anyway as creating this text was among the things we discussed on the maintainers summit 2017. BTW, is anyone wonders how the text looks processed, see https://www.kernel.org/doc/html/latest/admin-guide/reporting-issues.html – but remember, in a few areas it looks a bit different as it's missing the patches already in docs-next. Ohh, and yes, the text is quite long. But if you dislike that, please keep in mind that nobody has to read all of it from top to bottom: the TLDR and the step-by-step guide basically state all the important bits; the reference section explains each of the steps in more detail for those that need more details or just want to look something up. So, let the final(?) review begin! Ciao, Thorsten _______________________________________________ Ksummit-discuss mailing list Ksummitemail@example.com https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss
next reply other threads:[~2021-03-26 6:13 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-26 6:13 Thorsten Leemhuis [this message] 2021-03-26 6:15 ` [Ksummit-discuss] [1/5] reporting-issues: header and TLDR Thorsten Leemhuis 2021-03-26 6:23 ` Guenter Roeck 2021-03-26 9:41 ` Thorsten Leemhuis 2021-03-28 9:23 ` Thorsten Leemhuis 2021-03-28 10:03 ` Greg KH 2021-03-29 22:44 ` Jonathan Corbet 2021-03-30 5:59 ` Greg KH 2021-03-30 8:41 ` Thorsten Leemhuis 2021-03-26 6:16 ` [Ksummit-discuss] [2/5] reporting-issues: step-by-step-guide: main and two sub-processes for stable/longterm Thorsten Leemhuis 2021-03-26 8:57 ` Greg KH 2021-03-26 6:19 ` [Ksummit-discuss] [4/5] reporting-issues: reference section, stable and longterm sub-processes Thorsten Leemhuis 2021-03-26 6:19 ` [Ksummit-discuss] [5/5] reporting-issues: addendum Thorsten Leemhuis 2021-03-26 6:55 ` [Ksummit-discuss] FYI & RFC: obsoleting reporting-bugs and making reporting-issues official Thorsten Leemhuis 2021-03-26 6:57 ` [Ksummit-discuss] [3a/5] reporting-issues: reference section, main guide Thorsten Leemhuis 2021-03-26 6:59 ` [Ksummit-discuss] [3b/5] " Thorsten Leemhuis 2021-03-26 8:59 ` [Ksummit-discuss] FYI & RFC: obsoleting reporting-bugs and making reporting-issues official Greg KH 2021-03-26 9:48 ` Thorsten Leemhuis
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 * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [Ksummit-discuss] FYI & RFC: obsoleting reporting-bugs and making reporting-issues official' \ /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
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 NNTP newsgroup(s).