Bug#887454: Re-uploaded console-bridge

[Jochen Sprickerhof]

* Andreas Tille <tille at debian.org> [2018-02-17 22:30]:
>A not uploaded state has the target distribution "UNRELEASED".  Once it
>is uploaded this is set to "unstable" and the commit log says something
>like:
>
>    "Uploaded to unstable (or new)"
>
>I think that's pretty obvious vor everybody even without a tag.

We had the UNRELEASED discussion before, so there are obviously 
different ways to do it. But I would call an upload a release, as in you 
should not modify that version anymore and also don't use the same 
version number again for something different. So you might as well tag 
it. I don't see a benefit of putting the tag afterwards, rather it would 
make it harder for tools like git-buildpackage to find a reference point 
for a new version. Also note that packages might get uploaded and used 
on other sites, so it's useful to have the tag as a reference point.
If your way of doing it is really common practice, I would be glad to 
get some references for it. But otherwise we could just agree to have 
different views and stop this :).

>Its not about holding back version numbers.  As far as I know ftpmaster
>is not really happy about Debian revisions different from "-1".

Do you have a reference for this? Because I see some packages with 
higher numbers in there and one I uploaded recently with a -2 got 
accepted pretty quick without a complaint.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/debian-science-maintainers/attachments/20180218/b84a7028/attachment.sig>