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

Re: ruby-cmdparse



Am Mittwoch, den 11.11.2020, 03:16 +0100 schrieb Daniel Leidert:
> Am Mittwoch, den 11.11.2020, 00:42 +0100 schrieb Klaumi Klingsporn:
> > Am / On Tue, 10 Nov 2020 16:53:45 +0100
> > schrieb / wrote Daniel Leidert <dleidert@debian.org>:
> 
> [..]
> > The package builds now and the tests ran without errors :-)
> > Only a few lintian warnings which I fixed, only the ones
> > about missing nmu-entries are open.
> 
> You can add "Team upload." as top entry.

Team upload and releaes update entries should be above all other entries like
this:

ruby-cmdparse (3.0.6-1) UNRELEASED; urgency=medium

  * Team upload.
  * New upstream version (closes: #...)

  [Person 1]
  * changes ...

  [Person 2]
  * changes ...

  -- <date>

You can _definitely_ trim debian/changelog. A few hints:

- Changes to debian/.gitattributes, debian/gbp.conf and debian/salsa-ci.yml
don't need to be documented. They are only relevant to salsa and the
.gitattributes file actually makes sure they are not part of the source
package.

- Always use the presence form not the past.

- Don't use tabs (you seem to have used tabs).

- Entries which are superseeded by later actions can be removed. E.g. just keep
the latest entry for bumping the standards version.

- The entry regading the links refers to debian/ruby-cmdparse and not
to debian/ruby-cmdparse.links.

- I wouldn't use sublists. Personally I prefer a different approach (
https://salsa.debian.org/ruby-team/jekyll/-/blob/master/debian/changelog)

I'll build it soon. But it looks good to me so far.

Regards, Daniel
-- 
Regards,
Daniel Leidert <dleidert@debian.org> | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78

If you like my work consider sponsoring me via
https://www.patreon.com/join/dleidert

Attachment: signature.asc
Description: This is a digitally signed message part


Reply to: