From 30403aad7a9342e2377391d99056f4f95fe75729 Mon Sep 17 00:00:00 2001 From: Radoslav Dimitrov Date: Fri, 10 Jun 2022 15:16:47 +0300 Subject: [PATCH] docs: update the MAINTAINERS docs to address a TUF specification bump Signed-off-by: Radoslav Dimitrov --- docs/MAINTAINERS.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/docs/MAINTAINERS.md b/docs/MAINTAINERS.md index 9968fd39b..6725a5c6d 100644 --- a/docs/MAINTAINERS.md +++ b/docs/MAINTAINERS.md @@ -22,7 +22,7 @@ Versioning: Project management: -- Try to keep issues up-to-date with status updates! +- Try to keep issues up-to-date with status updates! - Feel free to ping open issues to check on them. - Use the "assignee" field to indicate when you are working on an issue. - Use GitHub issue labels to describe the issue (exact labels are still changing, so just look through and add those that seem like a good fit). @@ -45,4 +45,8 @@ Pre-merge (check everything again before hitting the merge button!): - This may be waived for PRs which only update docs or comments, or trivial changes to tests. - Make sure that the PR title, commit message, and description are updated if the PR changes significantly during review. +New version of the TUF specification: +- There's an automated workflow which monitors and opens an issue in case there's newer version of the [TUF specification](https://theupdateframework.github.io/specification/latest/)- Closing the issue should happen after completing the following steps: + - Review the changes to the specification and make sure they're addressed (possibly requires breaking out a few relevant issues). + - Bump the `tuf-version` in the `.github/workflows/specification-version-check.yml` workflow.