Steve Langasek [2014-06-13 14:33 -0700]: > This leaves Ubuntu devs with an unpleasant choice: do they slow down their > work in order to push all changes through the regular CI process, > eliminating the risk of regression from a no-change rebuild? Or do they get > the changes done in the archive efficiently, so that they don't have to > spend half a day (or more) handholding the change through the system?
I'd also be perfectly happy to just push to lp:project, but as these aren't really trunks but really just a read-only reflection of what's in the distro, I was told that this wouldn't work either. Would it work to push to lp:project *and* upload? Would the CI train consider this as a consistent change? Martin -- Martin Pitt | http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
signature.asc
Description: Digital signature
-- Mailing list: https://launchpad.net/~ubuntu-phone Post to : [email protected] Unsubscribe : https://launchpad.net/~ubuntu-phone More help : https://help.launchpad.net/ListHelp
