For a long time we have an issue with readiness of Release notes for a release. As the Documentation team is now working on automation of their tasks & infrastructure, @bex , as a representative of the Documentation team, has initiated a discussion on the Release notes topic. Me and @bex met and we came up with the following process for Release notes:
I would like to ask FESCo to review this policy (I plan to use it as an addendum to Changes Policy) and provide approval or comments. I am especially concern about point #4 , which enforces Release notes as a mandatory part of every Change.
Metadata Update from @jkurik: - Issue tagged with: meeting
Sounds good to me. Is there a description of the minimum requirements for a release not entry? Does a single sentence such as "Ruby was updated to version XY to match the lastest upstream release."?
Take a look at the example, draft, not finalized, issue template here: https://pagure.io/fedora-docs/release-notes/new_issue
In short release notes need to be useful to the domain expert and ideally useful to others who may get excited.
Makes sense to me.
I'm +1 to this proposal.
AGREED: Mandatory release notes are approved (+7,0,2) (nirik, 16:48:16)
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.