Consider deployment that is gate kept by a tag
Currently the workflow seems to be to ensure in reviews that changes to the terms are not those kind of changes that require an announcement (e.g. due to wording changes to the terms, or more substantial changes).
With a deployment method based on tags, e.g. using calver (such as 20230810
), we would minimize our trouble in regards to announce-worthy changes and figuring out "what the current version is".
I propose automatically deploying HEAD of the default branch not to https://terms.archlinux.org, but to some preliminary subdomain (e.g. https://staging.terms.archlinux.org or some such). Only tagged versions of the terms repository are deployed to https://terms.archlinux.org
This has the following benefits:
- we know (and also the user knows) exactly which version we have deployed (due to calver)
- we can diff very easily between HEAD and latest tag (and also mention this in an announcement mail to show to the user what the actual diff between the soon-to-be and current version of the terms is)
- we can ensure more easily to not deploy noteworthy changes by accident (because we can diff more specifically). a tag can therefore be seen as a form of quality gate