You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: DEVELOPMENT.md
+7-1Lines changed: 7 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -68,6 +68,7 @@ You may need to make changes to a pre-release prior to publishing a final stable
68
68
-`git checkout main`
69
69
-`git merge --no-ff release-next`
70
70
-`git push origin main`
71
+
-_Note:_ For the `v7.0.0` stable release, there will probably be a bunch of conflicts on `docs/**/*.md` files here because we have made changes to v6 docs but in `dev` we removed a lot of those files in favor of auto-generated API docs. To resolve those conflicts, we should accept the deletion from the `release-next` branch.
71
72
- Merge the `release-next` branch into `dev`**using a non-fast-forward merge** and push it up to GitHub
72
73
-`git checkout dev`
73
74
-`git merge --no-ff release-next`
@@ -90,11 +91,16 @@ After the `6.25.0` release, we branched off a `v6` branch for continued `6.x` wo
90
91
- Starting the release process for 6.x is the same as outlined above, with a few changes:
91
92
- Branch from `v6` instead of `dev`
92
93
- Use the name `release-v6` to avoid collisions with the ongoing v7 (pre)releases using `release-next`
93
-
- Do not merge `main` into the `release-v6` branch
94
+
-**Do not** merge `main` into the `release-v6` branch
94
95
- The process of the PRs and iterating on prereleases remains the same
95
96
- Once the stable release is out:
96
97
- Merge `release-v6` back to `v6` with a **Normal Merge**
98
+
-**Do not** merge `release-v6` to `main`
97
99
- Copy the updated changelog entry for the `6.X.Y` version to `main`
100
+
- Copy the docs changes to `main` so they show up on the live docs site for v6
0 commit comments