
On 02/02/13 14:11, Ian Lynagh wrote:
Hi Simon,
On Wed, Jan 30, 2013 at 03:04:06AM -0800, Simon Marlow wrote:
commit 1461d21ea3096e252fdd5698772dbfd1ad033d6a Author: Simon Marlow
Date: Thu Oct 4 16:07:27 2012 +0100 change notes
---------------------------------------------------------------
unix.cabal | 5 +++++ 1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/unix.cabal b/unix.cabal index 287caa8..1aaaec9 100644 --- a/unix.cabal +++ b/unix.cabal @@ -14,6 +14,11 @@ description: IEEE Std. 1003.1). . The package is not supported under Windows (except under Cygwin). + . + Changes in 2.7.0.0: + . + * @ProcessStatus@ changed to include a core-dumped flag. + extra-source-files: config.guess config.sub install-sh configure.ac configure
The unix version number is still 2.6.1.0, but doesn't the new policy http://hackage.haskell.org/trac/ghc/wiki/Repositories#Modifyinglocalpackages mean that it should be bumped to 2.7.0.0 now?
Yep, thanks for the reminder.
Also, what's the plan for the changelog? Is the package description going to accumulate entries, or just show those for the most recent version? Wouldn't it be better to include a CHANGES file instead?
I've got into the habit of putting change notes in the description field of the .cabal file, because they appear prominently in the Haddock docs, whereas a CHANGES file or similar is hard to find and tends to get forgotten (at least I tend to forget it). I don't have a specific rule for the number of versions to keep, but I suppose you wouldn't want the list to get too long. Cheers, Simon