Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Infra: Investigate Release Tagging #8

Open
2 tasks
sleevi opened this issue Jan 25, 2021 · 0 comments
Open
2 tasks

Infra: Investigate Release Tagging #8

sleevi opened this issue Jan 25, 2021 · 0 comments
Labels
infrastructure (Public) Issues with CA/B Forum Infrastructure

Comments

@sleevi
Copy link
Contributor

sleevi commented Jan 25, 2021

We should explore using release tags plus automation as a way of improving the experience for Chairs and Members.

Specifically, the following enhancements can be considered (note: will update this list based on discussion, as well as split into separate issues, the stuff we decide to go forward with)

  • Determine the release tag based on the Markdown YAML block version on a commit to the main repository
    • For example, if BR.md changed in the https://github.com/cabforum/servercert repository, and the version in the YAML preamble changed, we should be able to determine the release version of the BRs based on that, and automatically create a tag as appropriate.
  • Automate the generation of an IP review notice
    • When a new release tag is added with a specific suffix (e.g. "IPR"), even in a branch (such as used by the WG chair), add a comment to the PR that provides a copy/paste e-mail for the Chair to send for the IP review, with links to download and attach the relevant documents.
@sleevi sleevi added the infrastructure (Public) Issues with CA/B Forum Infrastructure label Jan 25, 2021
@sleevi sleevi added this to To do in Infrastructure Jan 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
infrastructure (Public) Issues with CA/B Forum Infrastructure
Projects
Infrastructure
  
To do
Development

No branches or pull requests

1 participant