ComputerSurge/bind9
3
0
Fork 0
Code Pull Requests 1 Activity

Update branch&tag naming convention in CONTRIBUTING

Browse Source 
(cherry picked from commit 5248a3e7db)
This commit is contained in:
Tom Krizek
2023-03-24 14:49:06 +01:00
parent c45ad643a5
commit 6b851c87fc
2 changed files with 8 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
CONTRIBUTING
View File

@@ -57,14 +57,14 @@ To clone the repository, use:
$ git clone https://gitlab.isc.org/isc-projects/bind9.git
Release branch names are of the form v9_X, where X represents the second
number in the BIND 9 version number. So, to check out the BIND 9.12
Release branch names are of the form bind-9.X, where X represents the
second number in the BIND 9 version number. So, to check out the BIND 9.18
branch, use:
$ git checkout v9_12
$ git checkout bind-9.18
Whenever a branch is ready for publication, a tag is placed of the form
v9_X_Y. The 9.12.0 release, for instance, is tagged as v9_12_0.
v9.X.Y. The 9.18.0 release, for instance, is tagged as v9.18.0.
The branch in which the next major release is being developed is called
main.

8
CONTRIBUTING.md
View File

@@ -71,14 +71,14 @@ To clone the repository, use:
> $ git clone https://gitlab.isc.org/isc-projects/bind9.git
Release branch names are of the form `v9_X`, where X represents the second
number in the BIND 9 version number. So, to check out the BIND 9.12
Release branch names are of the form `bind-9.X`, where X represents the second
number in the BIND 9 version number. So, to check out the BIND 9.18
branch, use:
> $ git checkout v9_12
> $ git checkout bind-9.18
Whenever a branch is ready for publication, a tag is placed of the
form `v9_X_Y`. The 9.12.0 release, for instance, is tagged as `v9_12_0`.
form `v9.X.Y`. The 9.18.0 release, for instance, is tagged as `v9.18.0`.
The branch in which the next major release is being developed is called
`main`.