Closed tomjaguarpaw closed 2 years ago
After today's meeting I understand that "stability" doesn't mean "API stability". Could we then clarify what exactly "stability" means in this context? I still don't really get it. It seems to mean something like "lack of churn".
"Lack of churn" is a pretty good summary actually -- that phrase featured heaviliy in the discussion that motivated the creation of the group. We really are interested in any disruptive influences on Haskell development, which could come from the core tools, other tools, breaking APIs, etc.
OK, looks like this PR can be closed as inapplicable then. But it would be helpful to make the following really painfully obvious somewhere in the README:
We really are interested in any disruptive influences on Haskell development, which could come from the core tools, other tools, breaking APIs, etc.
I think it makes sense to clarify, in the first paragraph, that this WG is about API stability (not "stability" as in whether services are available or whether software crashes).