You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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)
main
repositoryBR.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.The text was updated successfully, but these errors were encountered: