Proposal #625 Articulate stability goals, recommendation: strong accept

Moritz Angermann

4 Feb 2024 4 Feb '24

9:09 a.m.

Hi All, Pull request 625 (https://github.com/ghc-proposals/ghc-proposals/pull/625), is not a proposal as usual, but primarily amending the readme and principles. Simon has taken the Stability discussion we have had last year, and integrated the crystalized General Rules into the readme and principles. In my opinion, we have now debated this topic sufficiently, and found a formulation that captures the intent we want to set forward for the evolution of GHC. I think this spells out clear guardrails for GHCs evolution, as well as providing reassurance to commercial users of GHC regarding backwards compatibility and migration support though deprecation cycles when breakage is needed. As such, I strongly recommend acceptance of the proposal. While there has been a recent spark in discussion of warning flags, I do not believe that discussion to be productive towards the change this proposal tries to bring. I'd like to ask the committee to cast their final votes on this amendment to the readme and principles, by the end of the coming week. Unless someone objects, I'll merge this as it is now on the 10th of February. Best, Moritz

Attachments:

attachment.html (text/html — 1.5 KB)

Show replies by date

Eric Seidel

4 Feb 4 Feb

7:06 p.m.

New subject: Proposal #625 Articulate stability goals, recommendation: strong accept

I support acceptance, thank you Simon for writing this up! On Sun, Feb 4, 2024, at 03:09, Moritz Angermann wrote:

...

Hi All,

Pull request 625 (https://github.com/ghc-proposals/ghc-proposals/pull/625), is not a proposal as usual, but primarily amending the readme and principles. Simon has taken the Stability discussion we have had last year, and integrated the crystalized General Rules into the readme and principles.

In my opinion, we have now debated this topic sufficiently, and found a formulation that captures the intent we want to set forward for the evolution of GHC. I think this spells out clear guardrails for GHCs evolution, as well as providing reassurance to commercial users of GHC regarding backwards compatibility and migration support though deprecation cycles when breakage is needed. As such, I strongly recommend acceptance of the proposal.

While there has been a recent spark in discussion of warning flags, I do not believe that discussion to be productive towards the change this proposal tries to bring.

I'd like to ask the committee to cast their final votes on this amendment to the readme and principles, by the end of the coming week. Unless someone objects, I'll merge this as it is now on the 10th of February.

Best, Moritz _______________________________________________ ghc-steering-committee mailing list ghc-steering-committee@haskell.org https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee

Simon Marlow

5 Feb 5 Feb

8:02 a.m.

New subject: Proposal #625 Articulate stability goals, recommendation: strong accept

Agreed, let's do it! On Sun, 4 Feb 2024, 09:10 Moritz Angermann, wrote:

...

Hi All,

Pull request 625 (https://github.com/ghc-proposals/ghc-proposals/pull/625), is not a proposal as usual, but primarily amending the readme and principles. Simon has taken the Stability discussion we have had last year, and integrated the crystalized General Rules into the readme and principles.

In my opinion, we have now debated this topic sufficiently, and found a formulation that captures the intent we want to set forward for the evolution of GHC. I think this spells out clear guardrails for GHCs evolution, as well as providing reassurance to commercial users of GHC regarding backwards compatibility and migration support though deprecation cycles when breakage is needed. As such, I strongly recommend acceptance of the proposal.

While there has been a recent spark in discussion of warning flags, I do not believe that discussion to be productive towards the change this proposal tries to bring.

I'd like to ask the committee to cast their final votes on this amendment to the readme and principles, by the end of the coming week. Unless someone objects, I'll merge this as it is now on the 10th of February.

Best, Moritz _______________________________________________ ghc-steering-committee mailing list ghc-steering-committee@haskell.org https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee

Arnaud Spiwack

8:45 a.m.

New subject: Proposal #625 Articulate stability goals, recommendation: strong accept

I made a couple of (unessential) wording suggestions on the PR. At any rate, I think that we bikeshed this one long enough :-) . Let's adopt it. On Mon, 5 Feb 2024 at 09:03, Simon Marlow wrote:

...

Agreed, let's do it!

On Sun, 4 Feb 2024, 09:10 Moritz Angermann, wrote:

...
Hi All,

Pull request 625 (https://github.com/ghc-proposals/ghc-proposals/pull/625), is not a proposal as usual, but primarily amending the readme and principles. Simon has taken the Stability discussion we have had last year, and integrated the crystalized General Rules into the readme and principles.

In my opinion, we have now debated this topic sufficiently, and found a formulation that captures the intent we want to set forward for the evolution of GHC. I think this spells out clear guardrails for GHCs evolution, as well as providing reassurance to commercial users of GHC regarding backwards compatibility and migration support though deprecation cycles when breakage is needed. As such, I strongly recommend acceptance of the proposal.

While there has been a recent spark in discussion of warning flags, I do not believe that discussion to be productive towards the change this proposal tries to bring.

I'd like to ask the committee to cast their final votes on this amendment to the readme and principles, by the end of the coming week. Unless someone objects, I'll merge this as it is now on the 10th of February.

Best, Moritz _______________________________________________ ghc-steering-committee mailing list ghc-steering-committee@haskell.org https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee

_______________________________________________ ghc-steering-committee mailing list ghc-steering-committee@haskell.org https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee

-- Arnaud Spiwack Director, Research at https://moduscreate.com and https://tweag.io.

Richard Eisenberg

2:25 p.m.

New subject: Proposal #625 Articulate stability goals, recommendation: strong accept

Yes, let's accept. I agree that there may be further amendments as regards warnings, but this writeup is still a clear step forward (to me). On Mon, Feb 5, 2024 at 3:45 AM Arnaud Spiwack wrote:

...

I made a couple of (unessential) wording suggestions on the PR.

At any rate, I think that we bikeshed this one long enough :-) . Let's adopt it.

On Mon, 5 Feb 2024 at 09:03, Simon Marlow wrote:

...
Agreed, let's do it!

On Sun, 4 Feb 2024, 09:10 Moritz Angermann, wrote:

...
Hi All,

Pull request 625 ( https://github.com/ghc-proposals/ghc-proposals/pull/625), is not a proposal as usual, but primarily amending the readme and principles. Simon has taken the Stability discussion we have had last year, and integrated the crystalized General Rules into the readme and principles.

In my opinion, we have now debated this topic sufficiently, and found a formulation that captures the intent we want to set forward for the evolution of GHC. I think this spells out clear guardrails for GHCs evolution, as well as providing reassurance to commercial users of GHC regarding backwards compatibility and migration support though deprecation cycles when breakage is needed. As such, I strongly recommend acceptance of the proposal.

While there has been a recent spark in discussion of warning flags, I do not believe that discussion to be productive towards the change this proposal tries to bring.

I'd like to ask the committee to cast their final votes on this amendment to the readme and principles, by the end of the coming week. Unless someone objects, I'll merge this as it is now on the 10th of February.

Best, Moritz _______________________________________________ ghc-steering-committee mailing list ghc-steering-committee@haskell.org https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee

_______________________________________________ ghc-steering-committee mailing list ghc-steering-committee@haskell.org https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee

-- Arnaud Spiwack Director, Research at https://moduscreate.com and https://tweag.io. _______________________________________________ ghc-steering-committee mailing list ghc-steering-committee@haskell.org https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee

515

Age (days ago)

516

Last active (days ago)

List overview

Download

4 comments

5 participants

participants (5)

Arnaud Spiwack
Eric Seidel
Moritz Angermann
Richard Eisenberg
Simon Marlow