wholetrans/docs-matrix-spec
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Clarify what the release branch is used for, and how it should be named

Browse source
This commit is contained in:
Travis Ralston 2018-08-20 14:05:23 -06:00
parent ba51d5960e
commit 5b73a0174d
1 changed files with 4 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

8
meta/releasing_a_spec.md
View file

@ -5,10 +5,10 @@ specification, server-server specification, and identity server specification. E
of these gets released independently of each other with their own version numbers. of these gets released independently of each other with their own version numbers.
Once a specification is ready for release, a branch should be created to track the Once a specification is ready for release, a branch should be created to track the
changes in. This should be the name of the specification (as it appears in the directory changes in and to hold potential future hotfixes. This should be the name of the
structure of this project) followed by a forward slash and the version being released, specification (as it appears in the directory structure of this project) followed
followed by `_updates`. For example, if the Client-Server Specification was getting by "release-" and the release version. For example, if the Client-Server Specification
an r0.4.0 release, the branch name would be `client_server/r0.4.0_updates`. was getting an r0.4.0 release, the branch name would be `client_server/release-r0.4.0`.
*Note*: Historical releases prior to this process may or may not have an appropriate *Note*: Historical releases prior to this process may or may not have an appropriate
release branch. Releases after this document came into place will have an appropriate release branch. Releases after this document came into place will have an appropriate