Re: GHC 9.10 release schedule and core library status
Julian Ospald <[email protected]> Wed, 07 Feb 2024 02:24:22 +0000
| Newsgroups | gmane.comp.lang.haskell.libraries |
|---|---|
| Message-ID | <[email protected]> |
--===============0183638537508380333== Content-Type: multipart/alternative; boundary=----F5Q7HEIH61BNH2OBKAXPYA2M1LJ4KX Content-Transfer-Encoding: 7bit ------F5Q7HEIH61BNH2OBKAXPYA2M1LJ4KX Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi, Have all core/boot library maintainers been notified to join that mailing = list? Where is that information? I don't see it=2E The only reason I got wind of this is because H=C3=A9cate CCed the library= ML as well=2E I remain unconvinced that this is a good way of coordinating releases acro= ss 20+ maintainers=2E 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 branc= h? - 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=2E Thanks, Julian On February 5, 2024 2:28:16 PM UTC, Ben Gamari <ben@well-typed=2Ecom> wrot= e: >Julian Ospald <hasufell@posteo=2Ede> writes: > >> Hi, >> >> I'm unsure what the process here is=2E 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)=2E >> >We created the `ghc-releases` mailing list for the purpose of release >coordination=2E In the past I have also frequently created tracking >tickets in submodules' upstream repositories=2E 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=2E > >> 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=2E If that= is=20 >> too cumbersome, please link me to the place where I'm supposed to=20 >> comment and give me a deadline=2E >> >Sure, I will create a pair of tracking tickets=2E The proposed deadline i= s >before the second week in March=2E > >Cheers, > >- Ben ------F5Q7HEIH61BNH2OBKAXPYA2M1LJ4KX Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable <html><head></head><body><div dir=3D"auto">Hi,<br><br>Have all core/boot li= brary maintainers been notified to join that mailing list? Where is that in= formation? I don't see it=2E<br><br>The only reason I got wind of this is b= ecause H=C3=A9cate CCed the library ML as well=2E<br><br>I remain unconvinc= ed that this is a good way of coordinating releases across 20+ maintainers= =2E<br><br>Information that is necessary:<br><br>- what versions do YOU nee= d?<br>- what versions do maintainers want to see in the next GHC release?<b= r>- do maintainers want a "backport" of a version bump to an older GHC bran= ch?<br>- relationships between core libraries (that is the case for filepat= h)<br>- deadline<br><br>This could possibly be expressed in a shared spread= sheet, so that everyone understands the current status without going throug= h mailing lists they're not subscribed to or issue trackers with 10+ posts= =2E<br><br>Thanks,<br>Julian</div><br><br><div class=3D"gmail_quote"><div d= ir=3D"auto">On February 5, 2024 2:28:16 PM UTC, Ben Gamari <ben@well-typ= ed=2Ecom> wrote:</div><blockquote class=3D"gmail_quote" style=3D"margin:= 0pt 0pt 0pt 0=2E8ex; border-left: 1px solid rgb(204, 204, 204); padding-le= ft: 1ex;"> <pre class=3D"k9mail"><div dir=3D"auto">Julian Ospald <hasufell@posteo= =2Ede> writes:<br><br></div><blockquote class=3D"gmail_quote" style=3D"m= argin: 0pt 0pt 1ex 0=2E8ex; border-left: 1px solid #729fcf; padding-left: 1= ex;"><div dir=3D"auto"> Hi,<br><br> I'm unsure what the process here is=2E = Do you expect every boot library <br> maintainer to follow GHC issue tracke= r and comment there? Or to open a <br> PR against ghc repo? I definitely wo= n't do the latter as an unpaid <br> volunteer (I don't want to deal with GH= C MRs and CI)=2E<br><br></div></blockquote><div dir=3D"auto">We created the= `ghc-releases` mailing list for the purpose of release<br>coordination=2E = In the past I have also frequently created tracking<br>tickets in submodule= s' upstream repositories=2E I have not done that this<br>time as we have th= is mailing list but I would be happy to do so if this<br>would be preferabl= e=2E<br><br></div><blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0p= t 1ex 0=2E8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"><div dir= =3D"auto"> For 'filepath' and 'unix' (and 'os-string', which is to become a= boot <br> package) I'd prefer if you open issues on each issue tracker=2E = If that is <br> too cumbersome, please link me to the place where I'm suppo= sed to <br> comment and give me a deadline=2E<br><br></div></blockquote><di= v dir=3D"auto">Sure, I will create a pair of tracking tickets=2E The propos= ed deadline is<br>before the second week in March=2E<br><br>Cheers,<br><br>= - Ben<br></div></pre></blockquote></div></body></html> ------F5Q7HEIH61BNH2OBKAXPYA2M1LJ4KX-- --===============0183638537508380333== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KTGlicmFyaWVz IG1haWxpbmcgbGlzdApMaWJyYXJpZXNAaGFza2VsbC5vcmcKaHR0cDovL21haWwuaGFza2VsbC5v cmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL2xpYnJhcmllcwo= --===============0183638537508380333==--