> Am 10.05.2022 um 12:16 schrieb Miroslav Suchý <msuchy@xxxxxxxxxx>: > > The workflow exists: > > The Change proposal guide you how to suggest release notes. E.g. I have one change in this release and I wrote Yes, I know that. But, as far as I oversee, it’s not a (publication) workflow. E.g. there is no date when a text has to be delivered at latest, there is no one who checks it, there is no procedure what to do if something is missing, no date, when the final release note has to be completed, etc. It seems a more or less self-sustaining process. And there's no one publicly designated to be in charge - probably except poor Ben, who's in charge of everything no one else cares about. And that has often worked out well. So, the current state of release notes makes a rather incomplete impression, with a lot of empty chapters - just a few hours before release. But there a some hours left. Maybe, someone will fine-tuning it. -- Peter Boy https://fedoraproject.org/wiki/User:Pboy pboy@xxxxxxxxxxxxx CET (UTC+1) / CEST (UTC+2) Member of Fedora Server Edition WG Contributing to docs _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-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/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
