(Belated:) Release for v7.8 has begun

[John Clements]

(See note following template text:)

The release process for v7.8 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
v7.8.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
v7.8.0.1 and going up as usual), and pre-release builds will be
available shortly at

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

Please tell me if you think that this release is significant enough
that it should be announced on the users list for wider testing.

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

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

This e-mail is late, since it’s now the 15th. Pre-release builds are available, and have been for some time. If you need time to fix important bugs for the 7.8 release and you won’t have time to do it before the 17th, please please let me know by sending me e-mail.

It’s also perhaps worth noting that the e-mail suggests pushing history updates before the beginning of testing, a wonderful idea that we have not generally been implementing; if you get the chance in the next few days, it would be great if those of you responsible for history updates could do this before the beginning of testing.

Many thanks for your help in the build process!

John