-
Notifications
You must be signed in to change notification settings - Fork 698
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release checklist for 3.14.0.0 #10241
Comments
@ulysses4ever May I ask you to run the Pre-flight checks and report your findings? |
I'm happy to. My turnaround time these days is not great though. I'll try to shoot for evening today but worst case it's Monday... |
Actually, #10244 |
I updated the description with the list of regressions that may need to be fixed before the release. There are two so far... |
A third regression, sadly: #10046 |
Would it be possible to get a date when this release is going to be ready? |
Makes sense, especially if this is an interim release, between GHCs, with stress on Cabal the library not the tool. Still, this needs to be an informed decision. |
After today's meeting with @Mikolaj and @ulysses4ever, we have decided to reasonably aim for September 17. @mpickering does this suit the GHC release agenda? |
By the way, the timeline that works for the GHC team was discussed in #10193 And same for releasing the library only versus with the tool. |
For compatibility purposes, we need to integrate #10411 in our release of Cabal-syntax. This will warrant a patch release of Cabal-syntax to go alone with the cabal-install release, but does not need to happen until mid-October. @wz1000 will come back to us after some more testing has been done on the GHC side to confirm we can proceed with the patch release. GHC 9.12 is expected to be released mid-November, I would like cabal-install to be readily available on ghcup by this date. |
#10416 is an important fix for the 3.14 release. |
#10419 is also something we need fixed in the 3.14 series. |
#10559 there's one blocker about API changes, unless I'm missing something. |
This is the checklist of the 3.14.0.0 release, whose main highlight is Building profiled, dynamically-linked cabal projects #9900. The previous issue like this is for 3.12.
This lib:Cabal release is to help with the release of GHC 9.12, not to support its users. We are not releasing
cabal-install
for this release.The 3.16 release will be the one to support GHC users using GHC 9.12.
We will not do backports of user-facing features, unless they are blocking. CI fixes may be backported in order to facilitate the release process of GHC (especially on the Windows platform).
Considering the workload required, we aim for the 17th of September for full Hackage releases.
If an item is actionable, please create a sub-list of the PRs that relate to it.
It is not actionable, please write “not applicable” in parentheses on the same line.
Regressions we need to fix
Regression in HEAD leading to build path leaking into object files (preprocessors) #10242 (unreleased yet, only exists onmaster
)[3.12.0.0] Failed to find the installed unit #10046Change in behaviour in HEAD w.r.t copying and installation of executables in packages with Custom setups #9777dup for Agda specifically Regression in cabal-3.12.1.0:should be fixed downstream:cabal install --lib Adga
no longer works. #10235Regression:
cabal-3.12.1.0 install
ignores--program-suffix
when checking whether exe is already installed #10290GHC concerns
We are releasing
cabal-install
after the GHC release, but for matters of PVP compliance, we'll integrate GHC-specific changesCabal concerns
Tasks
master
.cabal-install
Backports
Side quests
regression in 3.14
attention: needs-backport 3.14
The text was updated successfully, but these errors were encountered: