Skip to content

Release Checklist 9.4

Matthew Flatt edited this page Nov 16, 2026 · 5 revisions

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.

[ ] Potential Blockers: https://github.com/racket/racket/issues/5652

History Updates

  • {John Clements clements@racket-lang.org}

    • Updates:
      • Stepper Updates: update HISTORY (updates should show v9.4 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 samth@ccs.neu.edu}

    • Typed Racket Updates: update HISTORY (updates should show v9.4 as the most current version; include the text "merge" in the commit message, or tell me if there are no such changes.)
  • {Matthias Felleisen matthias@ccs.neu.edu}

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

Testing

  • {Blockers}

  • {Robby Findler robby@cs.northwestern.edu}

    • DrRacket Tests:
    # from the top-level directory of the release bundle, run
    cd "$(dirname "$(./bin/racket -e '(display (collection-file-path "io.rkt" "tests" "drracket"))')")"
    chmod +x ./run.sh
    # adjust the RACKET environment variable to point to the right binary, eg:
    env RACKET=~/Desktop/Racket\ v6.3.90.900/bin/racket ./run.sh
    
    • Quickscript Tests:
    raco test -c quickscript
    raco test -c quickscript-test
    
    • Framework Tests:
    # from the top-level directory of the release bundle, run
    cd "$(dirname "$(./bin/racket -e '(display (collection-file-path "main.rkt" "framework" "tests"))')")"
    raco test .
    
    • Contracts Tests:
    env PLT_RUN_UNRELIABLE_TESTS=timing racket -l tests/racket/contract/all
    racket -l tests/racket/contract-stress-argmin
    racket -l tests/racket/contract-stress-take-right
    
    • Games Tests: play a bunch of games (not automated)
    • Teachpacks Tests: image tests
    racket -l 2htdp/tests/bitmap-as-image-in-universe
    racket -l 2htdp/tests/image-equality-performance-htdp
    racket -l 2htdp/tests/image-equality-performance
    racket -l 2htdp/tests/image-too-large
    racket -l 2htdp/tests/test-image
    
    • PLaneT Tests:
    # (the output of these tests is hard to read)
    raco test -l tests/planet/run-all
    
    • Redex Tests:
    racket -l redex/tests/run-tests
    # the results of color-tests require interpretation (and clicking)
    racket -l redex/tests/color-test
    
    • Pict Tests. Uncomment the tests disabled here then

      raco test -p pict pict-lib pict-doc pict-test
      
    • Release tests for the Windows release:

      • Test that the "Minimal Racket" source release compiles fine on x86 windows; follow the instructions in src/README.
      • Test that the "Minimal Racket" source release compiles fine on arm windows; follow the instructions in src/README.
      • Test that the "Racket" source release compiles fine on x86 windows; follow the instructions in src/README.
      • Test that the "Racket" source release compiles fine on arm windows; follow the instructions in src/README.
      • Test that all the x86 binary installers for work.
      • Test that all the arm binary installers for work.
    • Mac OS release tests

      • (first release of the year only) Test that the binary installer for 32-bit macOS works (copy the dmg contents, run raco pkg install -i drracket, start DrRacket)
  • {Sam Tobin-Hochstadt samth@ccs.neu.edu}

    • Match Tests:
    raco pkg install --skip-installed --auto racket-test
    raco test -l tests/match/main
    
    • Typed Racket Tests:
    raco pkg install --skip-installed --auto typed-racket-test
    racket -l typed-racket-test -- --all
    
    • Unit Contract Tests

      raco test -l tests/units/test-unit-contracts
      
    • Contract Region Tests

      racket -l tests/racket/contract/define-contract
      racket -l tests/racket/contract/with-contract
      
    • Class Contract Tests

      racket -l tests/racket/contract/class
      
    • EoPL Tests

      raco test -c eopl/tests
      
  • {Matthias Felleisen matthias@ccs.neu.edu}

    • Teachpacks Tests: check that new teachpacks are addable

      1. create foo.rkt: #lang racket (define x 0) (provide x)
      2. create bar.rkt: #lang htdp/bsl (require "foo.rkt") x; RUN and check for 0 to pop out
      3. delete require line, use teach pack menu to add foo.rkt; RUN and check for 0 to pop out
      4. delete foo.rkt and bar.rkt
      
    • Teachpack Docs: check teachpack docs in the bundles

      type "big-bang" into Definitions area, highlight, use F1; check for manuals 
      
    • Try teaching-languages testing framework (check-expect)

      run tests in plt: extra-pkgs/htdp/htdp-test/tests/test-engine/
      
    • Test #lang htdp/* languages

  • {Ryan Culpepper ryanc@racket-lang.org}

    • syntax-parse Tests

      raco test -c tests/stxparse
      
    • Data Tests

      raco test -c tests/data
      
    • Macro Debugger Tests

      racket -l tests/macro-debugger/all-tests -- --gui
      
    • RackUnit GUI Tests

      # not automated; use the Macro Stepper tests to exercise the RackUnit GUI
      
    • DB Tests

      # basic tests using sqlite3
      raco test -c tests/db
      # server-dependent tests: pg, my, etc
      ./share/pkgs/db-test/tests/db/bin/docker-util.sh pg     # start server
      racket -l tests/db/all-tests -- -t pg                   # run tests
      ./share/pkgs/db-test/tests/db/bin/docker-util.sh stop   # stop server
      
    • Rackunit Tests

      # note: some tests are intended to fail
      racket -l tests/rackunit/run-tests
      
    • SRFI Tests

      racket -l tests/srfi/run-tests
      
  • {John Clements clements@racket-lang.org}

    • 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.3.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)
      
  • {Jay McCarthy jay.mccarthy@gmail.com}

    • Web Server Tests

      raco test -c tests/web-server
      
    • XML Tests

      raco test -c tests/xml
      
    • HTML Tests

      raco test -c tests/html
      
    • PLAI Tests

      raco test -c plai
      
    • Racklog tests

      raco test -c racklog/tests
      
    • Datalog tests

      raco test -c datalog/tests
      
  • {Stephen Chang stchang@ccs.neu.edu}

    • 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 sperber@deinprogramm.de}

Clone this wiki locally