# Racket v8.11 Release Thread

**URL:** <https://racket.discourse.group/t/racket-v8-11-release-thread/2361>\
**Category:** Internals\
**Tags:** release-management\
**Created:** [October 3, 2023, 4:40am UTC](https://racket.discourse.group/t/racket-v8-11-release-thread/2361 "2023-10-03T04:40:12Z")\
**Posts on this page:** 11\
**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:** [October 3, 2023, 4:40am UTC](https://racket.discourse.group/t/racket-v8-11-release-thread/2361/1 "2023-10-03T04:40:12Z")

</div>

```
The release process for v8.11 will begin in about a week. 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:
- 7th: Branch day, merge window starts
- 15th: Merge window ends, testing starts
- 22nd: Testing ends

```

---

<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:** [October 16, 2023, 10:42am UTC](https://racket.discourse.group/t/racket-v8-11-release-thread/2361/2 "2023-10-16T10:42:37Z")

</div>

Hi John,

A small PR I made to quickscript got accepted and I’m wondering if it was too late for 8.11?

> <https://github.com/Metaxal/quickscript/pull/72#issuecomment-1763410876>
>
> Thank you Stephen!

Best

Stephen

---

<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:** [October 18, 2023, 5:19pm UTC](https://racket.discourse.group/t/racket-v8-11-release-thread/2361/3 "2023-10-18T17:19:10Z")

</div>

We haven't started testing yet, can you get Laurent to pick it for the release ? @Laurent.O

---

<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:** [October 18, 2023, 5:25pm UTC](https://racket.discourse.group/t/racket-v8-11-release-thread/2361/4 "2023-10-18T17:25:49Z")

</div>

More to the point, really: this should be Laurent's decision, not mine. To simplify this for Laurent, here's the script generated by Ryan's repo-manager-app for picking this:

```scheme
# create new release branch
git pull; git checkout -b release 1ada405d220a7cff7cadab392272ab3cb93fc781
git cherry-pick -x 5243a8740a6f22732f694427818bb3b3b9e363e5
git push origin release

```

And (my apologies for not responding sooner), I would very much like to start the testing some time before midnight here (PST) so it would be great if he could do this today? I realize it's already past the end of the workday in Europe.

---

<div class="post-metadata">

**Author:** ![Laurent.O](https://yyz2.discourse-cdn.com/free1/user_avatar/racket.discourse.group/laurent.o/32/18_2.png) [@Laurent.O](https://racket.discourse.group/u/Laurent.O)\
**Post date:** [October 18, 2023, 8:49pm UTC](https://racket.discourse.group/t/racket-v8-11-release-thread/2361/5 "2023-10-18T20:49:21Z")

</div>

Since Stephen's commit (5243a87) is already on head and is just the one above 1ada405 (as tagged by Ryan's script for release), isn't it possible to just branch to `release` directly from `5243a87` instead of cherry-picking?

> realize it's already past the end of the workday in Europe.

Well, it's not like Racket is my day job anyway 😉

---

<div class="post-metadata">

**Author:** ![Laurent.O](https://yyz2.discourse-cdn.com/free1/user_avatar/racket.discourse.group/laurent.o/32/18_2.png) [@Laurent.O](https://racket.discourse.group/u/Laurent.O)\
**Post date:** [October 18, 2023, 9:04pm UTC](https://racket.discourse.group/t/racket-v8-11-release-thread/2361/6 "2023-10-18T21:04:40Z")

</div>

Also, I see that Robby has been adding tags instead of using a release branch. So isn't a tag `v8.11` sufficient then?

edit: I added the tag. Let me know if something else needs to be done.

---

<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:** [October 18, 2023, 9:56pm UTC](https://racket.discourse.group/t/racket-v8-11-release-thread/2361/7 "2023-10-18T21:56:40Z")

</div>

1. In principle, creating a release tag directly on the given commit would probably work fine. Running the given commands, though, makes for uniformity; I can imagine a future in which we might scrape those commits, or something else. Basically: sure, you can do it differently, but why would you want to?

2. It _is_ important to create a branch, though; the cron job that checks to see whether it needs to update is looking for release branches only and not for an 8.11 tag (that would be extra redundant code, basically).

I have no desire to make extra work for you, though. Since it seems clear that you're implicitly approving adding this commit to the release, I went ahead and created the release branch for you (using a cherry-pick, sorry :)).

---

<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:** [October 18, 2023, 9:59pm UTC](https://racket.discourse.group/t/racket-v8-11-release-thread/2361/8 "2023-10-18T21:59:41Z")

</div>

I should add: there's a script that will add the 8.11 tag at the end of the release process. Having an existing 8.11 tag there will probably break the script, so I took the liberty of deleting it; apologies for unilaterally messing with your repo.

---

<div class="post-metadata">

**Author:** ![Laurent.O](https://yyz2.discourse-cdn.com/free1/user_avatar/racket.discourse.group/laurent.o/32/18_2.png) [@Laurent.O](https://racket.discourse.group/u/Laurent.O)\
**Post date:** [October 19, 2023, 9:17am UTC](https://racket.discourse.group/t/racket-v8-11-release-thread/2361/9 "2023-10-19T09:17:12Z")

</div>

All good, no worries at all, I was just wondering what's the simplest thing to do. Looks like I was confused about tags, if they are added automatically afterwards.

Thanks for fixing it! 🙂

---

<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:** [October 20, 2023, 11:38pm UTC](https://racket.discourse.group/t/racket-v8-11-release-thread/2361/10 "2023-10-20T23:38:42Z")

</div>

```
Testing for the v8.11 release
  (using the v8.10.900 release candidate build)

Search for your name on the checklist page to find relevant items, either
reply when you finish an item (please indicate which item/s is/are done),
or check it off yourself on the checklist page. Also, if you have any
commits that should have been picked, make sure that the changes are in.

Be sure to finish your testing by the 27th. Otherwise the release
will move on without your input.

The checklist page is at:
     https://github.com/racket/racket/wiki/Release-Checklist-8.11

Release candidates are at:
     https://pre-release.racket-lang.org

Please use these installers (or source bundles) -- don't test from
your own git clone (don't test the `master' branch by mistake!).
To get the tests, you can do this:

  cd ...racket-root...
  ./bin/raco pkg install -i --auto main-distribution-test

```

---

<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:** [October 20, 2023, 11:39pm UTC](https://racket.discourse.group/t/racket-v8-11-release-thread/2361/11 "2023-10-20T23:39:35Z")

</div>

EDIT: changed end of testing from 22nd to 27th, my apologies.
