Serge Hallyn [2013-11-13 14:55 -0600]: > Let's say three of us are working together on the next release of > package foo. While ironing out a new feature, we want to stash a > low prio bugfix to go into the same release. This happens quite > often, and a UDD branch that we can write to is a nice place to > stash these. Otherwise, yes, we simply need an out-of-band shared > tree. > > Of course then the importer has to deal with differences.
As long as you actually *use* the UDD branch, i. e. commit to it and use the usual dch -r/debcommit -r, the package importer won't do anything as the branch is already current. That's the intended meaning of a packaging VCS, and I consider the import robot to merely be a helper tool to catch up with uploads which weren't done with UDD (which are the great majority at the moment, though). > When I first started looking at UDD, it took me awhile to realize > that there was no way to feed a tag to the UDD branch to say 'now > build source packages and push from that to the archive' :) I would > have expected that, plus an error message on dput if there is a > conflict in the udd branch. That had been the plan all along when UDD was designed, but due to manpower issues it never got implemented. Martin -- Martin Pitt | http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel