[racket-dev] Pre-Release Checklist for v5.3, second call

From: Ryan Culpepper (ryan at cs.utah.edu)
Date: Wed Jul 25 16:28:29 EDT 2012

Checklist items for the v5.3 release
   (using the v5.2.900.1 release candidate build)

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

Important: new builds are created without announcement, usually whenever
I pick a few commits.  If you need to commit changes, please make sure
you tell me to pick it into the release branch.

--> Release candidates are at
-->   http://pre.racket-lang.org/release/installers

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 directory in such a directory, you can do this:
   cd ...racket-root...
   git archive --remote=git://git.racket-lang.org/plt.git release \
       -- collects/tests | tar x

----------------------------------------------------------------------

* Matthew Flatt <mflatt at cs.utah.edu>
   - JPR's test suite
   - Run COM tests
   - Try compiling with -funsigned-char
   Updates:
   - Update man pages in racket/man/man1: racket.1, gracket.1, raco.1
   Email me to pick the changes when they're done, or tell me if there
   are no such changes.

* John Clements <clements at brinckerhoff.org>
   - Stepper Tests
   Updates:
   - Stepper Updates: update HISTORY
   (updates should show v5.3 as the most current version; email me
   to pick the changes when they're done, or tell me if there are no such
   changes.)

* Matthias Felleisen <matthias at ccs.neu.edu>
   - Teachpacks Tests: check that new teachpacks are addable
   - Teachpack Docs: check teachpack docs in the bundles
   Updates:
   - Teachpack Updates: update HISTORY
   (updates should show v5.3 as the most current version; email me
   to pick the changes when they're done, or tell me if there are no such
   changes.)

* Noel Welsh <noelwelsh at gmail.com>
   - Rackunit Tests
   - SRFI Tests
   - Ensure that all claimed srfi's are in the installer and they all
     load into racket or drracket (as appropriate)

* Stephen Chang <stchang at ccs.neu.edu>
   - Lazy stepper tests

* Eli Barzilay <eli at barzilay.org>
   - XREPL Tests
   - Racket Tree: compare new distribution tree to previous one
   - Run the unix installer tests
   Version Updates: if a major change has happened, update the version
   number in:
   - racket/collects/mzscheme/info.rkt
   - racket/collects/mred/info.rkt

* Stephen Bloch <sbloch at adelphi.edu>
   - Picturing Programs Tests

* Jon Rafkind <rafkind at cs.utah.edu>
   Release tests for (one of the) linux releases:
   - Test that the `racket' and `racket-textual' source releases
     compile fine (note that they're still called `plt' and `mz' at
     this stage).
   - Test that the binary installers for both work, try each one in
     both normal and unix-style installation modes. (just ubuntu)
   [Note: get the release candidates from the URL in this email. Use
    the 'static table' link to see a list of all tar files available]

* Mike Sperber <sperber at deinprogramm.de>
   - DMdA Tests
   - Stepper Tests
   - Signature Tests

* Danny Yoo <dyoo at cs.wpi.edu>
   - Whalesong Tests (confirm that Whalesong runs from PLaneT)

Posted on the dev mailing list.