For one-time items such as blockers, it probably makes sense to check them off using github's markdown (that is, use the edit button to put an "x" between the square brackets. For all standard "testing" and "history" items that are copied from the template, though, please just go ahead and delete them entirely when they're done; since this list is long, it's otherwise difficult to locate the un-checked items.

• tracking issue : https://github.com/racket/racket/issues/5487

• {John Clements [email protected]}

  • Updates:
    • Stepper Updates: update HISTORY (updates should show v9.2 as the most current version; include the text "merge" in the commit message, or tell me if there are no such changes.)

• {Sam Tobin-Hochstadt [email protected]}

  • Typed Racket Updates: update HISTORY (updates should show v9.2 as the most current version; include the text "merge" in the commit message, or tell me if there are no such changes.)

• {Matthias Felleisen [email protected]}

  • Updates:
    • Teachpack Updates: update HISTORY (updates should show v9.2 as the most current version; include the text "merge" in the commit message, or tell me if there are no such changes.)

• {Blockers}

• {John Clements [email protected]}

  • Stepper Tests

  tests/stepper/run-manual-tests.rkt ;; run in DrRacket, ensure that expected failures occur.
  tests/stepper/manual-tests.txt ;; follow the instructions in this file
  

  • Linux source build:
    • Test that a randomly chosen racket source release compiles on linux Hint:

          ../configure --enable-bc --enable-cs
          make cs
          PLT_SETUP_OPTIONS="-j 1" make install-cs
          make bc
          PLT_SETUP_OPTIONS="-j 1" make install-bc
    

    • Test that a randomly chosen racket-minimal source release compiles on linux. Either this or the full build should be the builtpkgs bundle
    • Test that every binary installer for linux works in normal mode (install then start racket) [FIXME: is this enough?]
    • Test that a binary installer for linux works in unix-style mode (install then start racket) [FIXME: is this enough?]
  • Release tests for the Mac OS release:

    • On MacOS: Build from sources using the minimal distribution. First thing is to delete existing libraries you have for the test version, they will otherwise collide.

      rm -r ~/Library/Racket/9.1.900/
      cd src
      mkdir build
      cd build
      ../configure
      make
      make install
      cd ../..
      

      then

      ./bin/raco pkg install --auto -i racket-lib
      ./bin/raco pkg install --auto -i main-distribution
      

      (Why not just test the full source release? "The problem is that when packages are already included in a source bundle, then it doesn't include the right versions of packages that have to be platform-specific, such as the one that supplies "libintl.9.dylib".)

    • Test that every binary installer other than the 32-bit one for MacOS works (install, start DrRacket)

  • FrTime Tests (in frtime/demos) set language level to frtime before running
    • Test that expressions with time-varying values (e.g., seconds, (build-list (modulo seconds 10) identity)) render and update as expected in the FrTime language level. Check that they continue updating even after a garbage collection.
    • Test that a sampling of graphical demos (e.g., analog-clock.rkt, tetris.rkt) work as expected, responding to relevant key and mouse events and interactions with control widgets.
  • Inspect icons

    raco docs icons # then look at them (look for icons, ensure no red error text on the page)
    

• {Stephen Chang [email protected]}

  • Lazy Racket Tests

    raco test -l lazy/tests/main.rkt
    

  • Lazy stepper tests

    raco pkg install --skip-installed --auto htdp-test
    raco test -l tests/stepper/automatic-tests.rkt
    

• {Mike Sperber [email protected]}

  • DMdA Tests Test properties, World teachpack
  • Stepper Tests Check format of lists, records
  • Signature Tests Test signatures