On Fri, 2008-02-22 at 11:48 +0100, Bjorn Bringert wrote:

Perhaps we could show darcs change logs on hackage. For this we need a repository field in the .cabal file.

Yes, darcs changelog is a start, but it doesn't provide the kind of summary people usually want. Some people write summary changelogs though not many. One fully automatic thing would be a package differ, that looks at all api changes between versions of a package, or if they're only code changes then notes which functions changed. It's not full detail but it'd give package users an indication of whether it's a big api change or only a tweak in one data file. We'll need a package api diff program to help enforce the package versioning policy. Duncan

On Fri, 2008-02-22 at 13:03 +0100, Johan Tibell wrote:

On Fri, Feb 22, 2008 at 12:07 PM, Duncan Coutts wrote:

...

On Fri, 2008-02-22 at 11:48 +0100, Bjorn Bringert wrote:

...

Perhaps we could show darcs change logs on hackage. For this we need a repository field in the .cabal file.

Yes, darcs changelog is a start, but it doesn't provide the kind of summary people usually want.

It would be nice if you could provided some kind of CHANGES file with a package upload for that summary.

Sure, though realistically we'd not expect many maintainers to take advantage of such a feature unless there were some technical and social mechanism to encourage it. We have to make a tool to enforce the package version policy anyway (for those packages that opt-in) and one would expect that generating change summaries is not much harder. Duncan