Re: Sheriff Survey Results
On Friday, June 23, 2017 at 5:17:46 PM UTC+2, Boris Zbarsky wrote: > On 6/23/17 8:39 AM, Carsten Book wrote: > > We got a lot of Feedback thats its not easy to find out who is on > > "sheriffduty". We will take steps (like adding |sheriffduty tag to irc > > names etc) > > For what it's worth, searching IRC names is a bit of a pain. Can we > just throw the current sheriff nick in the topic of #developers or some > other channel? > > -Boris Yeah, good idea - already did that :) - Tomcat ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: The integration/autoland repo
Am Freitag, 1. Juli 2016 21:52:27 UTC+2 schrieb Henrik Skupin: > This gives problems if you have patches for different bugs but which > have overlapping code blocks. This requires you to keep already landed > commits around until code found its way to mozilla-central and > mozilla-inbound. Given that this can take up to a day or more I don't > feel satisfied right now in using autoland for my mozreview patches. > > -- > Henrik Yeah for this we will try to merge more often and in general have a strategy for this (gps already gave us sheriffs some kind of how-to). will add something next week on the sheriff wiki next week :) ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: The integration/autoland repo
Am Freitag, 1. Juli 2016 21:52:27 UTC+2 schrieb Henrik Skupin: > I'm just curious when autoland will actually be merged to > mozilla-central the first time. Given that we have this repository for a > while now, and sheriffs merged mozilla-central into it a couple of > times, I do not see any single merge of autoland to mozilla-central yet. > It's blocking some of my patches to reach Nightly builds. So for me the > current situation is not satisfying. > > Can you please clarify the merge strategy? > Hi Henrik you are totally wrong here. Short answer: we do merge autoland already since a few days. The thing that you "don't see" it has technically reasons. When m-c has not changed (like a direct backout on m-c) the first "merge" from a integration tree is not a hg merge its more a hg update (without the merge x to y) commit. This was always so and we did it also with b2g-inbound etc. The merge work is now the following 1.) update/merge autoland to m-c (as mentioned its not a hg merge commit in most cases) 2. the integration trees (mostly with fx-team and then inbound) follows *with* a hg merge and so commit. So yeah as short we do our work ;) - Tomcat ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: Just Autoland It
Note that we have problems on the tree due to https://bugzilla.mozilla.org/show_bug.cgi?id=1243276 - to avoid more problems from broken autolander landings we will set the trees to approval-only to avoid incomplete landings from autolander. - Tomcat ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Little Reminder regarding Pulsebot and Commits to Security Bugs
Hi, a little reminder that you still need to include/paste the commit url like https://hg.mozilla.org/integration/fx-team/rev/something to a security bug when you submit your checkin. Pulsebot can not make changes/comments to security bugs. This avoid confusion as example that i looks like a sheriff did the commit when a sheriff is marking the bug after a merge. Thanks :) - Tomcat ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Spoty Sheriff Coverage Monday February 16th
Hi due to a combination of PTO and Public Holiday in the US on Monday 16th full-time sheriff coverage is going to be spotty at this day. Please make an extra effort to keep an eye on any pushes you make. Thanks! -Tomcat ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
