From e220b50a1c56c8de1185672d54f6770bc8d3792a Mon Sep 17 00:00:00 2001 From: Jeremy Stretch Date: Mon, 6 Jan 2025 15:14:48 -0500 Subject: [PATCH] Clarify wording --- docs/development/getting-started.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/development/getting-started.md b/docs/development/getting-started.md index 53d8c2b2f..0b77bfd4d 100644 --- a/docs/development/getting-started.md +++ b/docs/development/getting-started.md @@ -42,7 +42,7 @@ The NetBox project utilizes two persistent git branches to track work: * `main` - All development on the upcoming stable (patch) release occurs here. Releases are published from this branch. * `feature` - All work planned for the upcoming minor release is done here. -Typically, you'll base pull requests off of the `main` branch, or off of `feature` if you're working on a new major release. For example, assume that the current NetBox release is v4.2.3. Work applied to the `main` branch will appear in v4.2.4, and work done under the `feature` branch will be included in the next minor release (v4.3.0). +Typically, you'll base pull requests off of the `main` branch, or off of `feature` if you're working on the upcoming minor or major release. For example, assume that the current NetBox release is v4.2.3. Work applied to the `main` branch will appear in v4.2.4, and work done under the `feature` branch will be included in the next minor release (v4.3.0). To create a new branch, first ensure that you've checked out the desired base branch, then run: