#43: Should we allow compatible API additions to a library in a minor release of
the platform?
--------------------+-------------------------------------------------------
Reporter: dons | Owner: dcoutts
Type: task | Status: new
Priority: major | Milestone: 2009.2.1
Component: Policy | Resolution:
Keywords: |
--------------------+-------------------------------------------------------
Old description:
> http://www.haskell.org/pipermail/libraries/2009-May/011605.html
>
> The question is this:
>
> Should we allow compatible API additions to a library in a minor
> release of the platform?
>
> The choice is between allowing only bug fixes in minor releases,
> or also allowing new features that add APIs but do not change
> any existing APIs.
>
> Discussion tracked on [email protected]
New description:
http://www.haskell.org/pipermail/libraries/2009-May/011605.html
The question is this:
Should we allow compatible API additions to a library in a minor
release of the platform?
The choice is between allowing only bug fixes in minor releases,
or also allowing new features that add APIs but do not change
any existing APIs.
Discussion tracked on [email protected]
Status:
|| Yay || Nay ||
|| [http://www.haskell.org/pipermail/libraries/2009-May/011606.html Axel
Simon] ||
[http://www.haskell.org/pipermail/libraries/2009-May/011607.html Felipe
Lessa] (maybe) ||
|| [http://www.haskell.org/pipermail/libraries/2009-May/011609.html Ganesh
Sittampalam] ||
[http://www.haskell.org/pipermail/libraries/2009-May/011610.html Magnus
Therning] (leaning) ||
|| [http://www.haskell.org/pipermail/libraries/2009-May/011611.html dons]
|| ||
--
Ticket URL: <http://trac.haskell.org/haskell-platform/ticket/43#comment:1>
haskell-platform <http://trac.haskell.org/haskell-platform>
The Haskell Platform: a comprehensive and robust collection of Haskell libraries
_______________________________________________
Haskell-platform mailing list
[email protected]
http://projects.haskell.org/cgi-bin/mailman/listinfo/haskell-platform
