debrelease doesn't tag and ensure source only build

I don't agree that debrelease should have primary responsibility for creating a tag. This is the job of 'debcommit --release' (usual workflow is hack; debcommit; hack; debcommit; dch -r; debcommit --release; debrelease -S). That said, it would be fair enough for debrelease either to refuse to upload if you haven't committed everything in your tree and tagged it, or to offer to run 'debcommit --release' for you.

On Fri, 2008-07-18 at 08:46 +0000, Colin Watson wrote:
> I don't agree that debrelease should have primary responsibility for
> creating a tag. This is the job of 'debcommit --release' (usual workflow
> is hack; debcommit; hack; debcommit; dch -r; debcommit --release;
> debrelease -S). That said, it would be fair enough for debrelease either
> to refuse to upload if you haven't committed everything in your tree and
> tagged it, or to offer to run 'debcommit --release' for you.

Oh. Well, by all means we should stay with the workflow people expect
from deb* tools. Still, it seems _weird_ to me that debcommit
--release != debcommit + debrelease.

-Rob

--
GPG key available at: <http://www.robertcollins.net/keys.txt>.

I do think they should be tied together somehow, and as I said I think it would be OK for debrelease to do the wrapping. One reason why they're separate at the moment is that a lot of developers have processes which look more like debcommit --release; test; debsign; debrelease (regardless of sanity ...).

debrelease should really be called debupload, given what it does at the moment! But it isn't.

Another thing that would be nice is for debrelease to automatically do -S when uploading to an ubuntu mirror. Perhaps that should be in another bug though.