Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • GHC GHC
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 4,828
    • Issues 4,828
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 447
    • Merge requests 447
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Releases
  • Analytics
    • Analytics
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Glasgow Haskell Compiler
  • GHCGHC
  • Issues
  • #19321

Closed
Open
Created Feb 04, 2021 by Ben Gamari@bgamari🐢Maintainer57 of 90 tasks completed57/90 tasks

Release tracking ticket for 9.2.1

This is the release checklist for the %9.2.1 milestone. See #16816 (closed) for the template that this was derived from.

Pre-fork checklist (major-only)

When forking a new release branch for a new major release series (e.g. ghc-9.0), please check the following:

  • Verify that haddock's development branch (namely the branch corresponding to GHC's previous major release, e.g. ghc-8.10) has been merged into ghc-head.
  • Create the new branch: git branch ghc-9.0
  • In the new branch bump the version number in configure.ac to, e.g., 9.0
  • In master bump the version number to that of the next development series, e.g., 9.1
  • Tag this master commit as, e.g., ghc-9.1-start
  • Push all of the above tags and branches

Pre-release checklist

  • (major-only) Remove the release notes for the previous release (e.g. docs/users_guide/8.6.*-notes.rst)
  • (major-only) Make release branch (e.g. ghc-8.8)
  • (major-only) Make post-release branch (e.g. ghc-8.9-start)
  • Ensure that submodules are on released tags (the below is produced using this script):
    • libraries/Cabal: todo (on 3.6.0.0)
    • libraries/Win32: version 2.12.0.1
    • libraries/array: todo (on v0.5.3.0-15-g3e4334a)
    • libraries/binary: version 0.8.9.0 (on 0.8.9.0)
    • libraries/bytestring: version 0.11.1.0
    • libraries/containers: todo (on v0.6.5.1)
    • libraries/deepseq: version 1.4.6 (on v1.4.6 although an uploaded is needed from @chessai)
    • libraries/directory: version 0.3.6.2 (on v0.3.6.2)
    • libraries/exceptions: needs revision (on v0.10.4-9-gebc21bd)
    • libraries/filepath: version 1.4.2.1, needs revision (on v1.4.2.1-ghc1-22-ge60969e)
    • libraries/haskeline: version 0.8.2
    • libraries/mtl: version 2.2.2
    • libraries/parsec: v3.1.14.0, needs revision (on v3.1.14.0)
    • libraries/pretty: version 1.1.3.6
    • libraries/process: version 1.6.13.2
    • libraries/stm: todo (on v2.5.0.0-ghc1-22-ge966ebb)
    • libraries/terminfo: needs revision (on 0.4.1.4-7-g9add7ed)
    • libraries/text: 1.2.5.1
    • libraries/time: version 1.11.1.1
    • libraries/transformers: version 0.5.6.2
    • libraries/unix: needs revision (on v2.7.2.2-r3-14-g21437f2)
    • libraries/xhtml: version 3000.2.2.1
    • utils/haddock: todo (on haddock-2.24.0-release-247-g2a966c8c)
    • utils/hsc2hs: todo (on v0.68.7-17-gfe518b0)
  • Non-released submodules up-to-date:
    • nofib
    • libffi-tarballs
    • libraries/integer-gmp/gmp/gmp-tarballs
  • Release notes (docs/users_guide/x.y.z-notes.rst) written
  • Release notes linked in docs/users_guide/index.rst
  • autoconf scripts updated
  • Check that Unicode database in base (libraries/base/cbits/README.Unicode) reflects current standard release (http://www.unicode.org/versions/latest/)
  • LlvmVersion in configure.ac is targetting intended LLVM version
  • Release notes mentions LLVM version requirement
  • llvm-targets file updated
  • Changelogs updated (these can be checked using .gitlab/linters/check-changelogs.sh):
    • libraries/ghc-prim
    • libraries/integer-gmp
    • libraries/integer-simple
    • libraries/hpc
    • libraries/base
  • Verify that the ~"backport needed" label has no more issues/merge requests needing backport
  • Verify that all CI builds are green before moving to release checklist

Release checklist

  • Push a provision provisional release commit to trigger the release builds using git push -o ci.variable="RELEASE_JOB=yes"
  • Wait until builds finish; verify that they finished successfully
  • Fetch release artifacts TODO: documentation
  • Sign and push release artifacts to downloads.haskell.org [TODO: documentation]
  • Make a release tag
  • Release/revise GHC-maintained libraries on Hackage [TODO: documentation]
    • libraries/base
    • libraries/ghc-prim
    • libraries/array
    • libraries/stm
    • libraries/ghc-heap
    • libraries/ghc-compact
    • libraries/ghc-boot
    • libraries/ghc-boot-th
    • libraries/hpc
    • libraries/libiserv
    • libraries/template-haskell
    • libraries/integer-gmp
    • libraries/integer-simple
  • Update ghc/homepage>:
    • Write download page (see ghc/homepage>)
    • Add news item to index.html
    • Add link to download.shtml
    • Look over changes locally
    • Add release announcement to GHC blog
    • Push changes to master
  • Announce on: GHC developers <ghc-devs@haskell.org>, GHC Users <glasgow-haskell-users@haskell.org>, Haskell Cafe <haskell-cafe@haskell.org>
  • Announce on: Haskell Discourse, /r/haskell, Twitter
  • Update latest symlink on downloads.haskell.org
  • Ensure that the Migration page is up-to-date

Post-release checklist

  • Update the Wiki status page
  • Update the language pragma history
  • Mark milestone as closed
  • Update /topic in #ghc
  • Update the VersionHistory wiki page
  • Set RELEASE=NO
  • Create a release tracking ticket for the next release using the template in #16816 (closed)
Edited Nov 01, 2021 by Ben Gamari
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking