HP 2012.4.0.0 -- Call for Proposals

Mark Lentczner mark.lentczner at gmail.com
Tue Aug 21 15:43:39 CEST 2012


While proposals for changes to Haskell Platform can be made at any time,
this call is for proposals that would like to land in the 2012.4.0.0
release.

The 2012.4.0.0 is scheduled for November 12th, 2012. In order for a
proposal to made it in that release, it needs to meet the following
timeline:

   - *August 20th, 2012* - Call for proposals for additions and changes
   - *September 17th, 2012* - Call for proposals ends (no more proposals
   considered)
   - *October 1st, 2012* - Proposals decided, Initial version list

*If you are a maintainer of a library that you'd like to be in the platform:
* Now is the time to get a clean version on Hackage, and then put together
a proposal for the haskell-platform list. Please see the process for Adding
Packages <http://trac.haskell.org/haskell-platform/wiki/AddingPackages>.

*Outstanding work:*

   - There is a proposal to include vector-0.9.1 in the platform
   - There is a ticket to consider including OpenGLRaw — Ticket
#167<http://trac.haskell.org/haskell-platform/ticket/167>
   - There are tickets to consider removing OpenGL and GLUT — Ticket
#57<http://trac.haskell.org/haskell-platform/ticket/57>,
   Ticket #58 <http://trac.haskell.org/haskell-platform/ticket/58>
   - There is a ticket about binary being in the platform without being
   part of it — Ticket #191<http://trac.haskell.org/haskell-platform/ticket/191>
   - There is a ticket about needing hscolour to build the platform, but it
   isn't part of it — Ticket
#160<http://trac.haskell.org/haskell-platform/ticket/160>

Please not that none of the tickets is a proposal before the list yet. If
the maintainer of those libraries, or someone else, want to propose a
change based on those tickets, now is the time to do so. In any event, I
will close those tickets on September 17th.

*If you are part of the reviewing process:* Traditionally, proposals have
been accompanied by lengthly discussions, often resulting in deep API
design confabs. As we are approaching a release, I'd like to ask all to
consider making this round more succinct if at all possible. In particular,
it would be great if proposals were keyed to specific revisions of a
library to be considered. If consensus is that something needs to be
changed before inclusion - it would be best if maintainers took that input
into account, turned another library version and placed that up for
consideration. Please note the schedule: I'm going to hold October 1st firm.

— Mark "proposed in a restaurant in front of friends" Lentczner
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/libraries/attachments/20120821/9c784d3f/attachment.htm>


More information about the Libraries mailing list