[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Best practices for changelogs


On Nov 20, 2007 2:54 AM, Paul TBBle Hampson <Paul.Hampson@pobox.com> wrote:
> I like to be able to use interdiff on my packages as well, and then
> on packages derived from my packages, or that were derived from the
> same package as my packages, and merging changelogs makes that that
> much harder.
> Anyway, this is only my personal preference. It boils down to "I
> avoid rewriting history" (based on something I imagined seeing in
> the Debian Policy, but which turned out to be me overreading
> something. ^_^)

  I thank everyone that brought something to this thread, that proved
very interesting to me. I had a few comments/requests to make:

  * I'm pretty sure now that both approaches are legitimate, so please
go on doing what you are doing, with the following little changes
  * please, when you are uploading a package to mentors, change the
distribution of the non-uploaded versions to UNRELEASED. That will
make it much clearer to anyone that the package has not been uploaded
(without having to resort to the PTS or rmadison - the latter being
down lately)
  * if you could state in your RFS if it is fine if the sponsor
'rewrites history' - that is merges all the contiguous toplevel
UNRELEASED entries, that would allow people like me who don't like
skipping versions to please themselves (while commiting the changes to
the SVN).

  What do you think about this ?

  Cheers, and thanks again for sharing your thoughts !


Reply to: