cc-oci-runtime
cc-oci-runtime copied to clipboard
intel
Automate release checklist tasks
Ideally, we'd have a script that could run the steps listed on the wiki here:
- https://github.com/01org/cc-oci-runtime/wiki/Release-Checklist
We're getting close to being able to automatically handle the OBS aspects (#672), which then leaves us with the question of whether we can automate the generation of the release notes.
We can at least generate the list of fixed bugs by:
- parsing
git logand looking forFixes:tags. - query the list of issues fixed between 2 dates. The latter is more exhaustive if we forget to put
Fixes:tags and will have false positives (issues we have closed but not fixed).
I'd vote for 1. and have everyone reminded about those Fixes: tags.
Agreed. I think as reviewers we should consider start requiring atleast one Fixes # in the commit messages.
@grahamwhaley, @sameo - what do you think? Should we require every PR to be coupled with an issue along with a Fixes # comment?
My thought was that, sure, auto-grabbing and filtering for 'fixes' and similar is good and fine - but, I also expect something will always slip through the net. I expect a final stage in the release process will always have to be a visual sanity check and xref to ensure the auto generated notes container all the right things (and none of the 'wrong things'). Automation good - but I don't think we can trust it 100% to generate the final notes without human review.
- but I don't think we can trust it 100% to generate the final notes without human review.
agree, we can't trust
As we enter into a more stable phase for COR, we do want PRs to be coupled with at least one issue. So I agree we should enforce the Fixes tag in PRs. We could even have pullapprove verify that for us.
I've raised #856 to update our contribution guidelines. See the same issue for details of pullapprove.