Haskell Platform: Changelogs and "available since"

Hi all, Reading a thread in -cafe made me think of another couple of requirements to consider for platform packages: * A changelog for the package is maintained * In the documentation for each function etc, the first version to support the feature is given. Thanks Ian

On Sat, Aug 8, 2009 at 7:46 PM, Ian Lynagh
* In the documentation for each function etc, the first version to support the feature is given.
I have often missed this when trying to pick a lower bound for my package dependencies. Creating a tool that computes this automatically would help the developers do this easily. -- Johan

Johan Tibell wrote:
On Sat, Aug 8, 2009 at 7:46 PM, Ian Lynagh
wrote: * In the documentation for each function etc, the first version to support the feature is given.
I have often missed this when trying to pick a lower bound for my package dependencies. Creating a tool that computes this automatically would help the developers do this easily.
It was proposed as a SoC project for this summer, but didn't make the cut: http://hackage.haskell.org/trac/summer-of-code/ticket/1565 I'd be more than happy to provide pointers/guidance if anyone wants to tackle this. Cheers, Simon

On Sat, Aug 8, 2009 at 10:06 PM, Simon Marlow
Johan Tibell wrote:
On Sat, Aug 8, 2009 at 7:46 PM, Ian Lynagh
wrote: * In the documentation for each function etc, the first version to support the feature is given.
I have often missed this when trying to pick a lower bound for my package dependencies. Creating a tool that computes this automatically would help the developers do this easily.
It was proposed as a SoC project for this summer, but didn't make the cut:
http://hackage.haskell.org/trac/summer-of-code/ticket/1565
I'd be more than happy to provide pointers/guidance if anyone wants to tackle this.
Cheers, Simon
I do volunteer for this. How can I get guidance? Regards, Laszlo

On Fri, 2009-08-14 at 15:34 +0200, Laszlo Nagy wrote:
I have often missed this when trying to pick a lower bound for my package dependencies. Creating a tool that computes this automatically would help the developers do this easily.
It was proposed as a SoC project for this summer, but didn't make the cut:
http://hackage.haskell.org/trac/summer-of-code/ticket/1565
I'd be more than happy to provide pointers/guidance if anyone wants to tackle this.
Cheers, Simon
I do volunteer for this. How can I get guidance?
Great! Do you use IRC? The #ghc IRC channel, the ghc users mailing list and cabal-devel mailing list would be great places to get guidance and feedback. Duncan

On 14/08/2009 21:00, Duncan Coutts wrote:
On Fri, 2009-08-14 at 15:34 +0200, Laszlo Nagy wrote:
I have often missed this when trying to pick a lower bound for my package dependencies. Creating a tool that computes this automatically would help the developers do this easily.
It was proposed as a SoC project for this summer, but didn't make the cut:
http://hackage.haskell.org/trac/summer-of-code/ticket/1565
I'd be more than happy to provide pointers/guidance if anyone wants to tackle this.
Cheers, Simon
I do volunteer for this. How can I get guidance?
Great!
Do you use IRC? The #ghc IRC channel, the ghc users mailing list and cabal-devel mailing list would be great places to get guidance and feedback.
Yes - and I think it would be a good idea to throw some ideas around first, and draft a design on the wiki before starting to hack something up. Cheers, Simon
participants (5)
-
Duncan Coutts
-
Ian Lynagh
-
Johan Tibell
-
Laszlo Nagy
-
Simon Marlow