Re: GHC 9.10 release schedule and core library status

Ben Gamari <[email protected]> Mon, 05 Feb 2024 09:28:16 -0500
Newsgroups gmane.comp.lang.haskell.libraries
Message-ID <[email protected]>
--===============2232784037421283176==
Content-Type: multipart/signed; boundary="=-=-=";
	micalg=pgp-sha256; protocol="application/pgp-signature"

--=-=-=
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

Julian Ospald <[email protected]> writes:

> Hi,
>
> I'm unsure what the process here is. Do you expect every boot library=20
> maintainer to follow GHC issue tracker and comment there? Or to open a=20
> PR against ghc repo? I definitely won't do the latter as an unpaid=20
> 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=20
> package) I'd prefer if you open issues on each issue tracker. If that is=
=20
> too cumbersome, please link me to the place where I'm supposed to=20
> 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,

=2D Ben

--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEE/lq2yR/qWXw7MRgLc+3p6M+67wEFAmXA8H0ACgkQc+3p6M+6
7wGWcAf/YCEWqWxTdRV4z//Zgr/2fJ6yI9vnDmvxAZ7z4ISwvTFSd46CP7hNcLPB
GtJUahvTtosjFHjlksx+M1OY6tbDYDkyai+Veyt9po/6EofChPFwC2W2i2F/l+um
Dg/Jey66SZEsX5+8zMbriY5OfJ1JQmTxQsJFMkINb3juyRTE7FD04MnbHpvhlLlH
qTKKXQ9g/YoZ8ob6s6yB5Eer/+maMnYC2B6TiAjqeHYCHhDMBSbDPJIrPIKVxW3r
J8ozo8f51Q6p9PlZDPnceR+sGeqveeINp8knbP0AKH70yw4orVFHEOlvfInNQakt
KW9YgVwdm/rvnuk1Xc2XwxgNJCkS6g==
=lr88
-----END PGP SIGNATURE-----
--=-=-=--

--===============2232784037421283176==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KTGlicmFyaWVz
IG1haWxpbmcgbGlzdApMaWJyYXJpZXNAaGFza2VsbC5vcmcKaHR0cDovL21haWwuaGFza2VsbC5v
cmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL2xpYnJhcmllcwo=

--===============2232784037421283176==--