Bug#871937: stretch-pu: package monkeysign/2.2.3
Control: tag -1 moreinfo
On Sat, Aug 12, 2017 at 14:21:11 -0400, Antoine Beaupre wrote:
> Package: release.debian.org
> Severity: normal
> Tags: stretch
> User: release.debian.org@packages.debian.org
> Usertags: pu
>
> Hi,
>
> I am working on a new release of Monkeysign, which I'd like to upload
> in Debian. If it would be just me, I would tag the current HEAD with
> 2.2.4, considering the changes are mostly minor and non-disruptive:
>
> angela:monkeysign$ git diff 2.2.3 --stat
> CONTRIBUTING.rst | 9 +-
> debian/gbp.conf | 2 +-
> doc/usage.rst | 4 +
> monkeysign/cli.py | 11 +-
> monkeysign/gpg.py | 35 ++--
> monkeysign/gtkui.py | 81 ++++++---
> monkeysign/tests/files/7B75921E.asc | 331 ++++++++++++++++++++-----------------
> monkeysign/tests/test_gpg.py | 21 +--
> monkeysign/tests/test_ui.py | 147 ++++++++++++-----
> monkeysign/ui.py | 168 ++++++++++++-------
> po/nl.po | 725 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 11 files changed, 1225 insertions(+), 309 deletions(-)
>
> as you can see, more than half of the diff (725 lines) is just a
> translation file update. The rest is fixes for tests and critical
> bugfixes (although the bugfixes have not been reported directly in the
> Debian BTS, but discovered through my own testing).
>
> Attached is the actual diff. Should I upload this as 2.2.4 to unstable
> and stable-pu? Or should i minimize this diff to a bare minimum and
> release a more targeted 2.2.4 to stable and a 2.3.0 to unstable?
>
There's no such thing as uploading the same package version to unstable
and proposed-updates. Please first get the changes in unstable, with
whatever version number. Let them sit for a while, and then come back
with a request for stable, with a description and justification of the
changes (which I couldn't see here).
Cheers,
Julien
Reply to: