Skip to content

Commit d2afcd7

Browse files
zimegzimeg
committed
docs: note the pattern of release branches in the maintainers guide
1 parent 3d66f92 commit d2afcd7

1 file changed

Lines changed: 2 additions & 0 deletions

File tree

‎.github/maintainers_guide.md‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -60,6 +60,8 @@ As a maintainer, the development you do will be almost entirely off of your fork
6060

6161
`main` is where active development occurs.
6262

63+
`release/vX.Y.Z` has the packaged distribution of a particular version based from the changes on `main`. This is created using a workflow when new releases are published.
64+
6365
When developing, branches should be created off of your fork and not directly off of this repository. If working on a long-running feature and in collaboration with others, a corresponding branch of the same name is permitted. This makes collaboration on a single branch possible, as contributors working on the same feature cannot push commits to others' open Pull Requests.
6466

6567
After a major version increment, there also may be maintenance branches created specifically for supporting older major versions.

0 commit comments

Comments
 (0)