Re: Best practices for changelogs
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Andres Mejia wrote:
> In any case, this debate will probably lead nowhere just like it did
> at debian-mentors
I think I was involved in that one. It ended up being a major point
of difference between myself and a potential sponsor for openjpeg.
> I'll continue to increment the changelog after each upload
> cycle to mentors.d.n and I'll inform anyone who's sponsoring
> accordingly. For one, because it's easy to use the proper
> dpkg-buildpackage options, both for maintainers and for sponsors, and
> two, because I think it's easier to find changes after each upload
> this way (sponsors can diff the diff for instance).
As a further point for the 'increment each time' case, I often give
out URLs and binary builds of packages I'm assembling for
sponsorship, and I want people who get them to _know_ whether I've
updated or not.
So as far as I'm concerned, once a package is uploaded somewhere as
a .diff.gz and a .dsc or a .deb, barring explicit notice to the
contrary, that version number represents something fixed in stone.
- --
- -----------------------------------------------------------
Paul "TBBle" Hampson, B.Sc, LPI, MCSE
Very-later-year Asian Studies student, ANU
The Boss, Bubblesworth Pty Ltd (ABN: 51 095 284 361)
Paul.Hampson@Pobox.com
Of course Pacman didn't influence us as kids. If it did,
we'd be running around in darkened rooms, popping pills and
listening to repetitive music.
-- Kristian Wilson, Nintendo, Inc, 1989
License: http://creativecommons.org/licenses/by/2.1/au/
- -----------------------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFHQSaLexDuohKLFuARApSjAJ9ZOodIKeU5FvEDoCdn5CS7stCG9gCfVlNJ
rLYfoXSXPU/qzPEqemoc7w4=
=sZPy
-----END PGP SIGNATURE-----
Reply to: