Dne 10. 05. 22 v 11:40 Peter Boy napsal(a):
Additionally, as fas as I see, docs team has no ==contentwise== workflow either
(and can’t provide one because it doesn’t govern the process). There is a
technical workflow, though, to ensure there is a file to be the next release
notes and a way to add content.
So the ==contentwise== workflow and responsibility should be part of the change
process and its governance.
Maybe, docs team can provide a lector (don’t know the english term, „editor in
chief“?) to finally fine-tune and format the text. But I suppose we explicitly
would have to find someone for each single release at the beginning of a
release cycle.
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
https://fedoraproject.org/wiki/Changes/RetiredPackages#Release_Notes
Wrangler (Ben) created
https://pagure.io/fedora-docs/release-notes/issue/759
So the content and workflow is available. I agree that it would nice to have
wrangler from documentation team who makes sure all documentation is added to
Release notes in time.
Miroslav
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
