# Racket v8.16 Release Thread

**URL:** <https://racket.discourse.group/t/racket-v8-16-release-thread/3468>\
**Category:** Internals\
**Tags:** release-management, release\
**Created:** [January 6, 2025, 12:21pm UTC](https://racket.discourse.group/t/racket-v8-16-release-thread/3468 "2025-01-06T12:21:31Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**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:** [January 6, 2025, 12:21pm UTC](https://racket.discourse.group/t/racket-v8-16-release-thread/3468/1 "2025-01-06T12:21:31Z")

</div>

```
The release process for v8.16 will begin in about four days. If you
have any new features that you want in and are relatively close to
to being done, now is a good time to do that.

Upcoming dates:
- 10th: Branch day, merge window starts
- 17th: Merge window ends, testing starts
- 25th: Testing ends

```

---

<div class="post-metadata">

**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:** [January 11, 2025, 10:11pm UTC](https://racket.discourse.group/t/racket-v8-16-release-thread/3468/2 "2025-01-11T22:11:00Z")

</div>

```
The release process for v8.16 has begun: release checkpoints have
been created for all packages in the main distribution, and release
branches have been created when necessary. You can go on using
`master` branches as usual. The main Racket repo's is now bumped to
v8.16.0.1 (to avoid having two different trees with the same version).

If you have any bug-fixes and changes (including history updates)
that need to go in the release then make sure to specify that in the
commit message by using the word `merge` or `release` or mail the
relevant repo manager [1]) the commit SHA1s. Do not push commits
directly to `release` branches.

Please make sure that code that you're responsible for is as stable
as possible, and let me know if there is any new work that should
not be included in this release.

      >>> NOW IS THE TIME TO FIX BUGS THAT YOU KNOW ABOUT <<<

The time between now and the end of the merge window is for fixing
new errors that prevent proper functioning of major components and
that show up during the preparation for a release. You can also
finalize piece of work that is not yet complete, but please avoid
merging new features.

Note that nightly builds will go on as usual (starting from
v8.16.0.1 and going up as usual), and pre-release builds will be
available shortly at

  https://pre-release.racket-lang.org/

[1] https://github.com/racket/racket/wiki/release-repo-managers

Upcoming dates:
- 17th: Merge window ends, testing starts
- 25nd: Testing ends

```

---

<div class="post-metadata">

**Author:** ![al\_shopov](https://avatars.discourse-cdn.com/v4/letter/a/ce73a5/32.png) [@al\_shopov](https://racket.discourse.group/u/al_shopov)\
**Post date:** [January 11, 2025, 10:41pm UTC](https://racket.discourse.group/t/racket-v8-16-release-thread/3468/3 "2025-01-11T22:41:27Z")

</div>

JFYI:  
I have created 2 pull requests for translatability of Quickscript messages:

[https://github.com/Metaxal/quickscript/pull/82](https://github.com/Metaxal/quickscript/pull/82)  
[https://github.com/racket/string-constants/pull/66](https://github.com/racket/string-constants/pull/66)

Given the timelines land may be done right after the release to allow:

- Time for proper review
- Time for translators

Regards:  
al\_shopov

На сб, 11.01.2025 г. в 23:21 John Clements via Racket Discourse \<[notifications@racket.discoursemail.com](mailto:notifications@racket.discoursemail.com)\> написа:

---

<div class="post-metadata">

**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:** [January 11, 2025, 10:52pm UTC](https://racket.discourse.group/t/racket-v8-16-release-thread/3468/4 "2025-01-11T22:52:32Z")

</div>

Sounds good to me (but also, I don't expect to be the one to merge these pull requests, so this is really a set of instructions for someone else ?)

---

<div class="post-metadata">

**Author:** ![robby](https://yyz2.discourse-cdn.com/free1/user_avatar/racket.discourse.group/robby/32/7_2.png) [@robby](https://racket.discourse.group/u/robby)\
**Post date:** [January 13, 2025, 12:55am UTC](https://racket.discourse.group/t/racket-v8-16-release-thread/3468/5 "2025-01-13T00:55:54Z")

</div>

I will be more than happy to merge these and I agree that doing after the release branch is created would be best, so they'll first appear in 8.17.

---

<div class="post-metadata">

**Author:** ![spdegabrielle](https://yyz2.discourse-cdn.com/free1/user_avatar/racket.discourse.group/spdegabrielle/32/95_2.png) [@spdegabrielle](https://racket.discourse.group/u/spdegabrielle)\
**Post date:** [January 13, 2025, 10:03am UTC](https://racket.discourse.group/t/racket-v8-16-release-thread/3468/6 "2025-01-13T10:03:58Z")

</div>

For those who don’t know, and might be interested, the release process is documented on the wiki at [Release overview · racket/racket Wiki · GitHub](https://github.com/racket/racket/wiki/Release-overview)

S.