The release process for v6.12 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
v6.12.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 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 release snapshot creation and the actual release 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
v6.12.0.1 and going up as usual), and pre-release builds will be
available shortly at
http://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
---
*REMINDER: PROCESS CHANGES*
In the interest of streamlining the release process, this release introduces
a few small changes to our usual process.
First, any updates to HISTORY files should be done during the regular merge
window, i.e., between now and the 15th, i.e., before the start of testing.
If you're not sure whether you're responsible for HISTORY file updates, please
consult the release checklist [1].
Second, there will be a fixed end date to the testing period, on the 22nd.
Please complete the tests you're responsible for before that point. If you do
not, I will make a best effort attempt at running them myself, and the release
will proceed without your input. If you're not sure whether you're responsible
for portions of testing, please consult the release checklist [1].
If you are responsible for either of those, and either cannot meet these
deadlines, or would rather not participate in releases in the future, please
get in touch.
[1] https://github.com/racket/racket/wiki/Release-Checklist-6.12
Upcoming dates:
- 15th: Merge window ends, testing starts
- 22nd: Testing ends
--
You received this message because you are subscribed to the Google Groups
"Racket Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to racket-dev+unsubscr...@googlegroups.com.
To post to this group, send email to racket-dev@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/racket-dev/m21sj1fxyd.wl-stamourv%40eecs.northwestern.edu.
For more options, visit https://groups.google.com/d/optout.
