On Wed, Oct 26, 2011 at 10:13 AM, Scott Kitterman <[email protected]> wrote: > On 10/26/2011 10:07 AM, Stefano Rivera wrote: >> >> Hi Scott (2011.10.26_16:01:15_+0200) >>>> >>>> One tool to rule them all. ;) >>> >>> It's probably a somewhat archaic view, but that's not a very Unix >>> like approach to the problem. If I was going to work on syncing a >>> package, I'd expect the tool for syncing packages to be the one I >>> wanted to use ... >> >> But there's a big overlap in functionality. Reviewing a merge and a sync >> both require test building, and a having a quick look at the diff and >> new changelog entries. >> >> Also, native syncs can't indicate sponsorship, yet (LP: #827555), so >> syncpackage isn't much help. > > For sponsoring, sure, but for your own uploads, not so much. > > I should probably remember I'm on break from Ubuntu development and not get > sucked into this, but I'll just throw out the idea that if sponsor-patch is > doing the job, then the issue isn't one of can/can't, but where the > functionality should most properly reside.
My impression is that sponsor-patch doesn't sync the package correctly indicating the bug filer as uploader, which is is the behavior that I'd like to see in syncpackage. I think it just sets the bug to confirmed, subscribes ubuntu-archive, and unsubscribes the sponsors team. As such, it has more to do with sponsoring rather than syncing. So sponsor-patch seems like a good bike shed to keep it in. Of course, I'm not sure as none of this seems documented. (Just filed LP: #882085) Thanks, -- Andrew Starr-Bochicchio Ubuntu Developer <https://launchpad.net/~andrewsomething> Debian Maintainer <http://qa.debian.org/developer.php?login=a.starr.b%40gmail.com> PGP/GPG Key ID: D53FDCB1 -- ubuntu-devel mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
