Schema for Release Tagging
I wanted to provide a definition for the construction of new release tags for CPAchecker [https://svn.sosy-lab.org/software/cpachecker/tags/].
There was a definition in
doc/Developing.md (see commit f3e49eea),
but that one did not satisfy the invariant for release tags
that I would like to have.
I added a schema to the CPAchecker documentation in commit f3e49eea [https://gitlab.com/sosy-lab/software/cpachecker/-/blob/trunk/doc/Developing.md#release-tagging].
There were several other ways used in the past. Let us discuss here which one is the best.
- Numerical month as the third number (old definition, see commit f3e49eea),
does not satisfy the invariant that smaller release tags should
refer to older commits.
Example: Suppose there is a
cpachecker-1.6from May 2016. Releases in December 2016 and January 2017 would then get the release tags
- Take the number of full months from major release. Satisfies the invariant. Currently checked in.
- Take the number of full months from January 1 of the year of the major release. Satisfies the invariant. Would be possible also, but the last few tags are using the current schema, and this would typically lead to large numbers.
@all What do you think?