Le 14/06/2014 11:25, Martin Pitt a écrit :
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?
Right, that's the main and best way to deal with it.
If there is no other commit to trunk since the last release, do you mind
about adding a tag about the upload version? That way CI Train won't
mention your change on the next upload :)
--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : [email protected]
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help : https://help.launchpad.net/ListHelp
