Le 10/02/2013 18:26, Mark Shuttleworth a écrit :
On 02/10/2013 02:59 AM, Sam Spilsbury wrote:
Okay, an update on this.
Thankfully, the automatic upload to distro saved the day on this one,
because I was able to use the latest snapshot by jenkins and restore
lp:compiz to r3602.
[snip]
I am pretty sure there was only one branch that went in after r3602,
and it was one of mine, which I've now marked as backed out.
However, I can unfortunately confirm that I do indeed have direct push
access AND overwrite access to lp:compiz, as does everyone else in
~compiz-team. That's really bad, because all it takes is one
misconfigured branch and you can unintentionally nuke trunk. I thought
that when we switched to using merge bots that all went away?
Good catch, thanks Sam. Yes, we can sort that out quickly. At a guess
Didrocks would know the right levers to pull in Launchpad.
Thanks Sam for your warning, appreciated :)
The good news is that we are fine, latest daily release was rev 3601
with the commit representing landing to distro being rev 3602, still on
lp:compiz. So we're all set :)
On the question on pushing to trunk, right, this is still possible and I
think we shouldn't let that (but it's currently a bigger debate). I
would like to include this change with refactoring of launchpad teams
for all projects from PS, as we have acquired over the years some
jungles of different teams working on different projects and I think,
it's going to be about time to have a cleaner, leaner launchpad team
organization. I plan to start that with a discussion in the incoming 2
months, once some rushy time (feature freeze, smart scopes landing…)
will be done.
After standardizing the packaging, standardizing our LP teams structure. ;)
Cheers,
Didier
--
Mailing list: https://launchpad.net/~unity-dev
Post to : [email protected]
Unsubscribe : https://launchpad.net/~unity-dev
More help : https://help.launchpad.net/ListHelp
