Re: Fedora 36 Release Notes, do we have some?
> Am 10.05.2022 um 12:16 schrieb Miroslav Suchý : > > 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 p...@uni-bremen.de CET (UTC+1) / CEST (UTC+2) Member of Fedora Server Edition WG Contributing to docs ___ 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
Re: Fedora 36 Release Notes, do we have some?
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
Re: Fedora 36 Release Notes, do we have some?
> Am 10.05.2022 um 10:47 schrieb Miro Hrončok : > > On Mon, May 9, 2022 at 11:17 PM Ben Cotton wrote: >> >> The #docs tag on Fedora Discussion is a better place to ask this >> question > > Noted. It's quite confusing to me to see that parts of our workflow > are not discussed here. 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. -- Peter Boy https://fedoraproject.org/wiki/User:Pboy p...@uni-bremen.de CET (UTC+1) / CEST (UTC+2) Member of Fedora Server Edition WG Contributing to docs ___ 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
Re: Fedora 36 Release Notes, do we have some?
On Mon, May 9, 2022 at 11:17 PM Ben Cotton wrote: > > The #docs tag on Fedora Discussion is a better place to ask this > question Noted. It's quite confusing to me to see that parts of our workflow are not discussed here. > but the F36 docs will be published to the website prior to > the release tomorrow. In the meantime, I've added them to the config > for docs.stg.fedoraproject.org, so you'll be able to see them there > after the next rebuild: > https://docs.stg.fedoraproject.org/en-US/fedora/f36/ Thanks. ___ 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
Re: Fedora 36 Release Notes, do we have some?
The #docs tag on Fedora Discussion is a better place to ask this question, but the F36 docs will be published to the website prior to the release tomorrow. In the meantime, I've added them to the config for docs.stg.fedoraproject.org, so you'll be able to see them there after the next rebuild: https://docs.stg.fedoraproject.org/en-US/fedora/f36/ -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ 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
Fedora 36 Release Notes, do we have some?
Hello. I have recently contributed to the Fedora 36 Release Notes [1] and I need to be able to link to that page. However, despite the release in less than a day, I still see no Fedora 36 Release Notes at https://docs.fedoraproject.org Is this a thing that is tracked and will happen when we release, or does something need to happen? [1] https://pagure.io/fedora-docs/release-notes/issue/808 -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok ___ 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
