From ben at well-typed.com  Mon Feb  5 14:28:16 2024
From: ben at well-typed.com (Ben Gamari)
Date: Mon, 05 Feb 2024 09:28:16 -0500
Subject: [GHC-Releases] GHC 9.10 release schedule and core library status
In-Reply-To: <6a7d9d6d-7511-9dea-9b96-243e5188caab@posteo.de>
References: <87a5ox1hq4.fsf@smart-cactus.org>
 <f144a2c0-7a19-46a7-8cf7-cd2401e2257b@glitchbra.in>
 <6a7d9d6d-7511-9dea-9b96-243e5188caab@posteo.de>
Message-ID: <8734u7ouiq.fsf@smart-cactus.org>

Julian Ospald <hasufell at posteo.de> writes:

> Hi,
>
> I'm unsure what the process here is. Do you expect every boot library 
> maintainer to follow GHC issue tracker and comment there? Or to open a 
> PR against ghc repo? I definitely won't do the latter as an unpaid 
> volunteer (I don't want to deal with GHC MRs and CI).
>
We created the `ghc-releases` mailing list for the purpose of release
coordination. In the past I have also frequently created tracking
tickets in submodules' upstream repositories. I have not done that this
time as we have this mailing list but I would be happy to do so if this
would be preferable.

> For 'filepath' and 'unix' (and 'os-string', which is to become a boot 
> package) I'd prefer if you open issues on each issue tracker. If that is 
> too cumbersome, please link me to the place where I'm supposed to 
> comment and give me a deadline.
>
Sure, I will create a pair of tracking tickets. The proposed deadline is
before the second week in March.

Cheers,

- Ben
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 487 bytes
Desc: not available
URL: <http://mail.haskell.org/pipermail/ghc-releases/attachments/20240205/b982a365/attachment.sig>

From ben at well-typed.com  Wed Feb  7 20:16:09 2024
From: ben at well-typed.com (Ben Gamari)
Date: Wed, 07 Feb 2024 15:16:09 -0500
Subject: [GHC-Releases] GHC 9.10 release schedule and core library status
In-Reply-To: <BFB3F679-6E99-4ADC-A21E-ACF4E4893104@posteo.de>
References: <87a5ox1hq4.fsf@smart-cactus.org>
 <f144a2c0-7a19-46a7-8cf7-cd2401e2257b@glitchbra.in>
 <6a7d9d6d-7511-9dea-9b96-243e5188caab@posteo.de>
 <8734u7ouiq.fsf@smart-cactus.org>
 <BFB3F679-6E99-4ADC-A21E-ACF4E4893104@posteo.de>
Message-ID: <87plx8f2t8.fsf@smart-cactus.org>

Julian Ospald <hasufell at posteo.de> writes:

> Hi,
>
> Have all core/boot library maintainers been notified to join that mailing list? Where is that information? I don't see it.
>
> The only reason I got wind of this is because Hécate CCed the library ML as well.
>
> I remain unconvinced that this is a good way of coordinating releases across 20+ maintainers.
>
> Information that is necessary:
>
> - what versions do YOU need?
> - what versions do maintainers want to see in the next GHC release?
> - do maintainers want a "backport" of a version bump to an older GHC branch?
> - relationships between core libraries (that is the case for filepath)
> - deadline
>
> This could possibly be expressed in a shared spreadsheet, so that
> everyone understands the current status without going through mailing
> lists they're not subscribed to or issue trackers with 10+ posts.
>
That sounds like a fine idea. I would be happy to put together such a
spreadsheet if others would find this useful.

Cheers,

- Ben

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 487 bytes
Desc: not available
URL: <http://mail.haskell.org/pipermail/ghc-releases/attachments/20240207/4a383d8e/attachment.sig>

From hasufell at posteo.de  Wed Feb  7 02:24:22 2024
From: hasufell at posteo.de (Julian Ospald)
Date: Wed, 07 Feb 2024 02:24:22 +0000
Subject: [GHC-Releases] GHC 9.10 release schedule and core library status
In-Reply-To: <8734u7ouiq.fsf@smart-cactus.org>
References: <87a5ox1hq4.fsf@smart-cactus.org>
 <f144a2c0-7a19-46a7-8cf7-cd2401e2257b@glitchbra.in>
 <6a7d9d6d-7511-9dea-9b96-243e5188caab@posteo.de>
 <8734u7ouiq.fsf@smart-cactus.org>
Message-ID: <BFB3F679-6E99-4ADC-A21E-ACF4E4893104@posteo.de>

Hi,

Have all core/boot library maintainers been notified to join that mailing list? Where is that information? I don't see it.

The only reason I got wind of this is because Hécate CCed the library ML as well.

I remain unconvinced that this is a good way of coordinating releases across 20+ maintainers.

Information that is necessary:

- what versions do YOU need?
- what versions do maintainers want to see in the next GHC release?
- do maintainers want a "backport" of a version bump to an older GHC branch?
- relationships between core libraries (that is the case for filepath)
- deadline

This could possibly be expressed in a shared spreadsheet, so that everyone understands the current status without going through mailing lists they're not subscribed to or issue trackers with 10+ posts.

Thanks,
Julian

On February 5, 2024 2:28:16 PM UTC, Ben Gamari <ben at well-typed.com> wrote:
>Julian Ospald <hasufell at posteo.de> writes:
>
>> Hi,
>>
>> I'm unsure what the process here is. Do you expect every boot library 
>> maintainer to follow GHC issue tracker and comment there? Or to open a 
>> PR against ghc repo? I definitely won't do the latter as an unpaid 
>> volunteer (I don't want to deal with GHC MRs and CI).
>>
>We created the `ghc-releases` mailing list for the purpose of release
>coordination. In the past I have also frequently created tracking
>tickets in submodules' upstream repositories. I have not done that this
>time as we have this mailing list but I would be happy to do so if this
>would be preferable.
>
>> For 'filepath' and 'unix' (and 'os-string', which is to become a boot 
>> package) I'd prefer if you open issues on each issue tracker. If that is 
>> too cumbersome, please link me to the place where I'm supposed to 
>> comment and give me a deadline.
>>
>Sure, I will create a pair of tracking tickets. The proposed deadline is
>before the second week in March.
>
>Cheers,
>
>- Ben
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/ghc-releases/attachments/20240207/3bbe4085/attachment-0001.html>

From andrew.lelechenko at gmail.com  Tue Feb 20 01:11:09 2024
From: andrew.lelechenko at gmail.com (Andrew Lelechenko)
Date: Tue, 20 Feb 2024 01:11:09 +0000
Subject: [GHC-Releases] GHC 9.10 release schedule and core library status
In-Reply-To: <CAHFo2uoguJYQKHdcMzvV48OjVkhcF0BeZLGEny9xzdwPSoabnQ@mail.gmail.com>
References: <87a5ox1hq4.fsf@smart-cactus.org>
 <9F3AC138-DE67-4F17-8BEE-3CC50E24CA35@gmail.com>
 <CAHFo2uoguJYQKHdcMzvV48OjVkhcF0BeZLGEny9xzdwPSoabnQ@mail.gmail.com>
Message-ID: <CE798282-1E72-4579-B2A8-89F1A7DE8984@gmail.com>

Thanks, Ben, for pushing through version bumps for `filepath` and `containers`. We also released new versions of `bytestring` and `text` last week. 

Mikolaj, what’s the schedule for Cabal 3.12? https://gitlab.haskell.org/ghc/ghc/-/wikis/GHC-status#11-major-releases says that all major releases should be reflected as submodules in GHC source tree before GHC fork date, which is AFAIU this Friday.

Best regards,
Andrew

> On 23 Jan 2024, at 08:32, Mikolaj Konarski <mikolaj at well-typed.com> wrote:
> 
>> * Mikolaj, are we looking for Cabal 3.12 or carrying on with 3.10.3+? There are at least two important features missing from Cabal 3.10: semaphores and multiple home units.
> 
> We plan to have Cabal 3.12 in time.
> 
> On Tue, Jan 23, 2024 at 12:59 AM Andrew Lelechenko
> <andrew.lelechenko at gmail.com> wrote:
>> 
>> Thanks, Ben. (I’m not subscribed to mail lists CC’d, so I expect this reply to be missing from them)
>> 
>> CC’ng Matthew Craven on behalf of bytestring, Xia Li-yao on behalf of text, Lei Zhu, Carsten König and Miao ZhiCheng on behalf of array (it’s not orphaned).
>> 
>> Several blockers from the top of my head:
>> 
>> * Bump containers submodule to 0.7, long overdue. AFAIR blocked on https://github.com/judah/haskeline/pull/186 - Ben, are you able to merge it?
>> 
>> * Bump filepath submodule to 1.5 and add os-string to boot libraries. Julian might remember better, but AFAIR there are no blockers, just someone has to upgrade several submodules at once.
>> 
>> * GHCJS progress depends on merging outstanding PRs for bytestring and text to provide pure Haskell implementations, and I imagine Sylvain (CC’d) would wish them to be merged and released before GHC 9.10 is forked.
>> 
>> * Mikolaj, are we looking for Cabal 3.12 or carrying on with 3.10.3+? There are at least two important features missing from Cabal 3.10: semaphores and multiple home units.
>> 
>> Best regards,
>> Andrew
>> 
>> On 22 Jan 2024, at 16:00, Ben Gamari <ben at well-typed.com> wrote:
>> 
>> Hi all,
>> 
>> First, apologies for the silence regarding the 9.10 fork; I was hoping
>> to improve our communications with boot library authors in the run-up to
>> GHC 9.10 but illness unfortunately took me largely out of commission for
>> a first few weeks of the year. Happily, things are looking rosier now.
>> 
>> Having had a chance to look at the 9.10 branch and the release goals, I
>> am planning to cut the fork for GHC 9.10 around a month from today, on
>> 23 Februrary 2024. This leaves around a month of time to merge the
>> `ghc-internals` split and a few of the other bits of work that remain
>> outstanding. We anticipate the first alpha release will come a week
>> after the fork (see the Milestone [1] for further details).
>> 
>> How does this sound to you?
>> 
>> For organizational purposes, it would be helpful if we designated a
>> coordinating maintainer for each of our boot packagers for the 9.10 release.
>> My understanding is that our boot libraries have the following primary
>> maintainers but don't hesitate to let me know if you believe this to be
>> incorrect:
>> 
>> | Package         | Maintainer                 |
>> | --------------- | -------------------------- |
>> | Cabal           | Mikolaj Konarski           |
>> | Win32           | Tamar Christina            |
>> | array           | (orphaned)                 |
>> | binary          | Lennart Kolmodin?          |
>> | bytestring      | Andrew Lelechanko          |
>> | containers      | David Feuer                |
>> | deepseq         | Melanie Phoenix            |
>> | directory       | Phil Rufflewind            |
>> | exceptions      | Ryan Scott                 |
>> | filepath        | Julian Ospald              |
>> | haddock         | Hecate                     |
>> | haskeline       | Judah Jacobson             |
>> | hpc             | David Binder               |
>> | mtl             | Emily Pillmore             |
>> | parsec          | Oleg Grenrus               |
>> | process         | Michael Snoyman            |
>> | stm             | Simon Marlow               |
>> | terminfo        | Judah Jacobson             |
>> | text            | Andrew Lelechanko          |
>> | time            | Ashley Yakeley             |
>> | transformers    | Ross Paterson              |
>> | unix            | Julian Ospald              |
>> 
>> It would be great if each maintainer could let me know what they would
>> like to do for the 9.10 release. In general we would love to have the
>> set of boot libraries pinned down at least in version by the second
>> alpha, which we are planning for the second week of March 2024. Does
>> this sound reasonable?
>> 
>> As always, I would encourage core library maintainers to be conservative
>> in their plans for a GHC release and avoid introducing major features or
>> refactorings in their release. Such changes both add risk to the release
>> schedule and complicate the users' migration paths; consequently, they
>> are ideally best held for releases asynchronous to the GHC release
>> process.
>> 
>> Thanks again for all of your work!
>> 
>> Cheers,
>> 
>> - Ben
>> 
>> 
>> [1] https://gitlab.haskell.org/ghc/ghc/-/milestones/380#tab-issues
>> 
>> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/ghc-releases/attachments/20240220/47c9c0ce/attachment-0001.html>

From mikolaj at well-typed.com  Tue Feb 20 09:46:29 2024
From: mikolaj at well-typed.com (Mikolaj Konarski)
Date: Tue, 20 Feb 2024 10:46:29 +0100
Subject: [GHC-Releases] GHC 9.10 release schedule and core library status
In-Reply-To: <CE798282-1E72-4579-B2A8-89F1A7DE8984@gmail.com>
References: <87a5ox1hq4.fsf@smart-cactus.org>
 <9F3AC138-DE67-4F17-8BEE-3CC50E24CA35@gmail.com>
 <CAHFo2uoguJYQKHdcMzvV48OjVkhcF0BeZLGEny9xzdwPSoabnQ@mail.gmail.com>
 <CE798282-1E72-4579-B2A8-89F1A7DE8984@gmail.com>
Message-ID: <CAHFo2uo=P7JoFJFbouEZkBP29dGLHpCvM2zKi6Ff6f7chPrFEw@mail.gmail.com>

> Mikolaj, what’s the schedule for Cabal 3.12?

The schedule is that we are looking for a release manager
for 3.12.1 and waiting for the release of 3.10.3 in order
not to perform two releases concurrently.

> https://gitlab.haskell.org/ghc/ghc/-/wikis/GHC-status#11-major-releases says that all major releases should be reflected as submodules in GHC source tree before GHC fork date, which is AFAIU this Friday.

That means cabal is going to be late. If that helps,
3.12.1 will be forked off the current master branch
and, at this time, we don't plan to remove any features
or other commits before the release.

Cheers,
Mikolaj

From ben at well-typed.com  Thu Feb 29 22:57:21 2024
From: ben at well-typed.com (Ben Gamari)
Date: Thu, 29 Feb 2024 17:57:21 -0500
Subject: [GHC-Releases] GHC 9.10.1 alpha 1 delay
Message-ID: <87o7bydgkx.fsf@smart-cactus.org>

Hi all,

Unfortunately due to persistent trouble merging the last few patches
destined for 9.10.1-alpha1 I will need to delay the release by a few
days. As I will be away for the first two days of next week I will be
delaying by one week, placing the new alpha 1 release date on 7 March
2024.

Cheers,

- Ben
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 487 bytes
Desc: not available
URL: <http://mail.haskell.org/pipermail/ghc-releases/attachments/20240229/0025405c/attachment.sig>