> That's what I'll do when sponsoring bileto updates, but if other people
> want to do it the .dsc way then I won't argue with them, I just think it's
> harder work.
We can do both, depending on what the sponsor prefers I think.
The reason I said to use the .dsc was also to make sure that the
and merged, based on top of my current work as well (and pushed 3.30)
--
https://code.launchpad.net/~3v1n0/ubuntu/+source/gnome-session/+git/gnome-session/+merge/354136
Your team Ubuntu Desktop is requested to review the proposed merge of
In my opinion it's enough for the sponsor to be the person that authored the
(signed) tag, so no need to make sponsoring bileto uploads even harder by
requiring a round trip through the .dsc to fix a finalise commit.
That's what I'll do when sponsoring bileto updates, but if other people want
Didier, this can be merged as bileto is in proposed now...
Then if you want to be the commiter of the changelog finalisation, just import
the new dsc.
--
https://code.launchpad.net/~3v1n0/ubuntu/+source/gnome-session/+git/gnome-session/+merge/354136
Your team Ubuntu Desktop is requested to
