Skip to content

Commit ba8290e

Browse files
Update references to LTS from v1.6 to v1.10 (#56729)
1 parent efa917e commit ba8290e

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

CONTRIBUTING.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -278,8 +278,8 @@ Be sure to change the UUID value back before making the pull request.
278278

279279
The process of [creating a patch release](https://docs.julialang.org/en/v1/devdocs/build/distributing/#Point-releasing-101) is roughly as follows:
280280

281-
1. Create a new branch (e.g. `backports-release-1.6`) against the relevant minor release
282-
branch (e.g. `release-1.6`). Usually a corresponding pull request is created as well.
281+
1. Create a new branch (e.g. `backports-release-1.10`) against the relevant minor release
282+
branch (e.g. `release-1.10`). Usually a corresponding pull request is created as well.
283283

284284
2. Add commits, nominally from `master` (hence "backports"), to that branch.
285285
See below for more information on this process.
@@ -291,8 +291,8 @@ The process of [creating a patch release](https://docs.julialang.org/en/v1/devdo
291291
the pull request associated with the backports branch. Fix any issues.
292292

293293
4. Once all test and benchmark reports look good, merge the backports branch into
294-
the corresponding release branch (e.g. merge `backports-release-1.6` into
295-
`release-1.6`).
294+
the corresponding release branch (e.g. merge `backports-release-1.10` into
295+
`release-1.10`).
296296

297297
5. Open a pull request that bumps the version of the relevant minor release to the
298298
next patch version, e.g. as in [this pull request](https://github.com/JuliaLang/julia/pull/37718).

0 commit comments

Comments
 (0)