[SCM] calf audio plugins packaging branch, master, updated. debian/0.0.18.5-1-13-g1771d8e
Jonas Smedegaard
dr at jones.dk
Tue Aug 24 17:07:17 UTC 2010
On Tue, Aug 24, 2010 at 06:29:18PM +0200, Adrian Knoth wrote:
>On Tue, Aug 24, 2010 at 06:16:24PM +0200, Jonas Smedegaard wrote:
>
>>> + [ Jonas Smedegaard ]
>>> + * Tidy copyright file: Adjust a few stanzas and declare it formatted
>>> + according to draft DEP5 rev135.
>>> + * Fix add a missed owner to copyright file (no new licenses).
>>> + * Drop local CDBS snippets and locally declared DEB_MAINTAINER_MODE:
>>> + All part of main CDBS now.
>>> + * Refer to FSF website (not postal address) in rules file header.
>>> + * Fix ALSA build-dependency auto-resolving (CDBS no longer horribly
>>> + executes control.in file as a shell script).
>>> + * Improve watch file: Add usage comment; relax pattern to non-digit
>>> + versions and non-gzip tarball compression.
>>> + * Fix DEP5 synatx of copyright file: append ./ in all files sections.
>>> + * Improve copyright file: Refer to FSF website (not postal address),
>>> + and put reference below Debian-specific comment to hint that it is
>>> + not verbatim copied.
>>
>> Please another time look at possibilities of merging entries when
>> doing git-dch.
>>
>> I would have merged and compacted the multiple changes to copyright
>> file in above.
>
>Damn, you're right. Are we hitting a corner case here? With distributed
>development, the original author probably knows best what's simply
>cosmetics and what's worth to appear in the changelog.
>
>Given that I usually don't remember what I've done a couple of months
>ago, I tend to add the changelog entries shortly after a period of
>work, that is, when I think I'm not going to touch the package for the
>next few weeks.
>
>Would it make sense, as a rule of thumb or even a team guideline, to
>provide changelog entries when done with editing instead of using
>git-dch just right before the upload? While the latter might work with
>a single maintainer, I don't see how it could with multiple people
>touching a package over several months.
>
>
>Anyway, I'll pay more attention next time.
I think we are both right: It makes sense *both* to update changelog
after finishing a round of work *and* right before release.
I obviously got distracted back then: Today when I noticed your (many
attempts at) upload, I looked at my local git and found some additional
copyright file improvements that I hadn't commit'ed yet. :-)
- Jonas
--
* Jonas Smedegaard - idealist & Internet-arkitekt
* Tlf.: +45 40843136 Website: http://dr.jones.dk/
[x] quote me freely [ ] ask before reusing [ ] keep private
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-multimedia-maintainers/attachments/20100824/a47933e4/attachment.pgp>
More information about the pkg-multimedia-maintainers
mailing list