On Sat, Nov 06, 2021 at 11:55:39PM -0700, Adam Williamson wrote: > * Acknowledged and had a definite plan to replace the existing tooling > and practices at least at the same level as currently. Okay, cool. Can you help me better define the "at the same level" benchmark? My stab at things that needed to make sure the new way meshes with the current process: 1. The new process needs to make sure that Bugzilla entries with CommonBugs keyword are triaged in a timely manner. 2. When proposed Common Issues* are accepted, the whiteboard field in Bugzilla is updated. 3. All accepted entries need to follow a consistent format, ideally using some form of templating. 4. We need templates to deal with special cases like those which require installer images, or where a workaround is needed even when an update is available. 5. Entries need to be updated with instructions when a candidate fix is available. 6. And further updated when a fix is released. 7. We figure out something to do about archiving at EOL time. (Although this doesn't necessarily need to be in place until... F38. Could be part of a general plan to archive older topics on Ask Fedora.) 8. We have new documentation covering the new procedures. 9. We have tooling in place and/or people commited to cover all of the above. 10. More automation would be lovely, but at least we don't want it _less_ automated than the current state. Does that cover it? What did I miss. > * Came with people attached who are definitely committed to working on > the implementation and all the work of writing issues, wrangling > replies, tagging things, aging things out... Definitely have people _interested_. I'll see about _committed_. :) I'm not proposing we do this until we hit the appropriate time in the F36 schedule, so I guess ~ beta freeze. That gives some time to line things up. Adam, would you be _interested_ in helping update the scripts and creating automation, if you had work time to do it? What would the tradeoffs be? Also: although this isn't a change to Fedora Linux... maybe I should run this through the Changes process? * Bikeshedding tangent: I prefer "Common Issues" to "Common Bugs", because it's broader and there's less potential for conflict between different possible technical and less-technical definitions of "bug". Like, I'm seeing some people On The Internet say, with apparent straight faces, that "bugs" are found during the testing phase and that once it's in production, it's a "defect" not a "bug". -- Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx> Fedora Project Leader _______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
