Re: Call for GHC Maintainers
Thanks for the note. I will be happy to pitch in. Thanks, Hemanth On Tue, 11 Aug 2020, 07:40 Moritz Angermann, wrote: > Hi there! > > As it stands right now, Ben is the one who works tirelessly trying to > cut releases. Not just for the most recent version, but also for > previous versions. Most recently 8.10.2, but we have 9.0 coming up as > well. > > I know that there are some people who deeply care for personal or > professional reasons for older releases, 8.4, 8.6, 8.8, ... Some of > them have stacks of patches applied, or proprietary extensions. I'd > argue that most of those applied patches are backports of bug fixes > and rarely language features, as language features will break > compatibility (due to ghc, base, and other library versions anyway). > > I would therefore like drum up a group of people who will take care > (ideally 2+ per release) of backporting and making minor partch > releases. This does not have to go on forever, but it would take much > needed load off of Ben to focus on what ever happens in ghc HEAD. > > So what would this work actually look like? It would consist of > - going through the list of MRs and tagging those which are relevant > for backporting to a certain release. > - backport MRs where the MR does not cleanly apply. > - fixup any test-suite failures. > - agree on a date to cut/make the release. > > This is not a permanent commitment. I hope we can attract more people > to the ghc release managers. > > I'm looking forward to great many responses. And I'm sure Ben will be > able to help mentor us through cutting the first releases. I'll > volunteer to be part of the 8.6 branch maintainers for now. > > Cheers, > Moritz > > PS: There is a slightly related discussion about release cadence and > versions and how other projects deal with this in this ticket: > https://gitlab.haskell.org/ghc/ghc/-/issues/18222 > ___ > ghc-devs mailing list > ghc-devs@haskell.org > http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs > ___ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
Re: Call for GHC Maintainers
Hello devs, I may be under-qualified for this sort of task but I’d be happy to pitch in if you find it useful. — Best regards, Artem Pelenitsyn On Mon, Aug 10, 2020 at 10:10 PM Moritz Angermann < moritz.angerm...@gmail.com> wrote: > Hi there! > > As it stands right now, Ben is the one who works tirelessly trying to > cut releases. Not just for the most recent version, but also for > previous versions. Most recently 8.10.2, but we have 9.0 coming up as > well. > > I know that there are some people who deeply care for personal or > professional reasons for older releases, 8.4, 8.6, 8.8, ... Some of > them have stacks of patches applied, or proprietary extensions. I'd > argue that most of those applied patches are backports of bug fixes > and rarely language features, as language features will break > compatibility (due to ghc, base, and other library versions anyway). > > I would therefore like drum up a group of people who will take care > (ideally 2+ per release) of backporting and making minor partch > releases. This does not have to go on forever, but it would take much > needed load off of Ben to focus on what ever happens in ghc HEAD. > > So what would this work actually look like? It would consist of > - going through the list of MRs and tagging those which are relevant > for backporting to a certain release. > - backport MRs where the MR does not cleanly apply. > - fixup any test-suite failures. > - agree on a date to cut/make the release. > > This is not a permanent commitment. I hope we can attract more people > to the ghc release managers. > > I'm looking forward to great many responses. And I'm sure Ben will be > able to help mentor us through cutting the first releases. I'll > volunteer to be part of the 8.6 branch maintainers for now. > > Cheers, > Moritz > > PS: There is a slightly related discussion about release cadence and > versions and how other projects deal with this in this ticket: > https://gitlab.haskell.org/ghc/ghc/-/issues/18222 > ___ > ghc-devs mailing list > ghc-devs@haskell.org > http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs > ___ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
Re: Call for GHC Maintainers
Moritz, Moritz Angermann writes: > I know that there are some people who deeply care for personal or > professional reasons for older releases, 8.4, 8.6, 8.8, ... Some of You skipped GHC 8.2 ;-) In any way, I'd be interested in helping making GHC 8.2.3+ happen! Cheers, Herbert signature.asc Description: PGP signature ___ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
Re: Call for GHC Maintainers
Hi, I always appreciate maintainers' hard works. I'd like to support GHC releases and some tasks. Is there anything that I could do? PS My haskell time is limited to nights and weekends, so my works are slow. (I can't access to haskell community in the day job...) Regards, Takenobu On Tue, Aug 11, 2020 at 11:10 AM Moritz Angermann wrote: > > Hi there! > > As it stands right now, Ben is the one who works tirelessly trying to > cut releases. Not just for the most recent version, but also for > previous versions. Most recently 8.10.2, but we have 9.0 coming up as > well. > > I know that there are some people who deeply care for personal or > professional reasons for older releases, 8.4, 8.6, 8.8, ... Some of > them have stacks of patches applied, or proprietary extensions. I'd > argue that most of those applied patches are backports of bug fixes > and rarely language features, as language features will break > compatibility (due to ghc, base, and other library versions anyway). > > I would therefore like drum up a group of people who will take care > (ideally 2+ per release) of backporting and making minor partch > releases. This does not have to go on forever, but it would take much > needed load off of Ben to focus on what ever happens in ghc HEAD. > > So what would this work actually look like? It would consist of > - going through the list of MRs and tagging those which are relevant > for backporting to a certain release. > - backport MRs where the MR does not cleanly apply. > - fixup any test-suite failures. > - agree on a date to cut/make the release. > > This is not a permanent commitment. I hope we can attract more people > to the ghc release managers. > > I'm looking forward to great many responses. And I'm sure Ben will be > able to help mentor us through cutting the first releases. I'll > volunteer to be part of the 8.6 branch maintainers for now. > > Cheers, > Moritz > > PS: There is a slightly related discussion about release cadence and > versions and how other projects deal with this in this ticket: > https://gitlab.haskell.org/ghc/ghc/-/issues/18222 > ___ > ghc-devs mailing list > ghc-devs@haskell.org > http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs ___ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
