# Racket v8.7 Release Thread **URL:** \ **Category:** Internals\ **Tags:** release-management, dev\ **Created:** [October 2, 2022, 3:38pm UTC](https://racket.discourse.group/t/racket-v8-7-release-thread/1343 "2022-10-02T15:38:22Z")\ **Posts on this page:** 1\ **Showing post:** 22
**Author:** ![jbclements](https://yyz2.discourse-cdn.com/free1/user_avatar/racket.discourse.group/jbclements/32/11_2.png) [@jbclements](https://racket.discourse.group/u/jbclements)\ **Post date:** [November 11, 2022, 8:20pm UTC](https://racket.discourse.group/t/racket-v8-7-release-thread/1343/22 "2022-11-11T20:20:19Z")
Thinking about this a bit more. I kind of like the fact that currently, the `master` branch has a single thread. I realize that merge commits that are made with merge -s ours don't represent "real" dependencies, but that's not obvious unless you dig into the commits and see that the merge has no diff. So I'm inclined to drop back to the "merge-with-the-release-branch-when-its-created" strategy. I'd really like to hear from others, though. @samth ? @mflatt ? This should probably be a separate topic... --- _[View the full topic](https://racket.discourse.group/t/racket-v8-7-release-thread/1343)._