From: Tom Krizek <tkrizek@isc.org>
Date: Fri, 24 Mar 2023 13:49:06 +0000 (+0100)
Subject: Update branch&tag naming convention in CONTRIBUTING
X-Git-Tag: v9.19.12~60^2
X-Git-Url: http://git.ipfire.org/gitweb/index.cgi?a=commitdiff_plain;h=5248a3e7dbbb0040e1f976ff06525eff175ad377;p=thirdparty%2Fbind9.git

Update branch&tag naming convention in CONTRIBUTING
---

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 0b7661b6717..4b3db893811 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -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`.