Closed Bug 964172 Opened 8 years ago Closed 8 years ago

Merge mozmill-tests branches for Firefox 27 release

Categories

(Mozilla QA Graveyard :: Mozmill Tests, defect, P1)

defect

Tracking

(firefox27 fixed, firefox28 fixed, firefox29 fixed)

RESOLVED FIXED
Tracking Status
firefox27 --- fixed
firefox28 --- fixed
firefox29 --- fixed

People

(Reporter: andrei, Assigned: andrei)

Details

Tracking but for merging the mozmill-tests branches for the upcoming Firefox 27 release.

27th January: Beta => Release
3rd February: Aurora => Beta
              Nightly => Aurora 

Detailed schedule:
https://mail.mozilla.com/home/publiccalendar@mozilla.com/Releases%20Scheduling.html
As a small update.
The merge from Beta to Release took a long time to complete.

The guys had some blockers, one of them being bug 964578 (which I see is now fixed).
I had a chat with :bajaj on IRC to keep up do date with the merge.

Unfortunately by 3:50 AM it wasn't still done.

I just woke up at 7:50 ish and it seems its finally done, yet the trees are still closed because of an infra issue (I had setup some monitoring tools alerting me when the trees get reopened).

It seems I missed when they actually done the merge.

I now pushed our changes for mozilla-beta to mozilla release.
http://hg.mozilla.org/qa/mozmill-tests/rev/3fb5b79c1353 (mozilla-beta) tag
http://hg.mozilla.org/qa/mozmill-tests/rev/131603fec811 (mozilla-release) merge
http://hg.mozilla.org/qa/mozmill-tests/rev/33a476fcf808 (mozilla-release) tag

We'll need to retrigger the some tests.
In total we had 8 testsruns (OSX functional and remote) that ran before I managed to push the merge.

I've retriggered all of them, so we're good.
(In reply to Andrei Eftimie from comment #1)
> The guys had some blockers, one of them being bug 964578 (which I see is now
> fixed).
> I had a chat with :bajaj on IRC to keep up do date with the merge.
> Unfortunately by 3:50 AM it wasn't still done.

Thanks Andrei! Given that we should not depend on such crazy hours, we will have to work on some kind of automation which can actually do the merge for us. I put this topic into our goals proposal but it will most likely not make Q1.
Well no one needs to stand up that late.

At that hour we only needed to run `hg push` once the merge has been actually done.
I'm not sure we can fully automate this.

A reliable notification once the merge has been completed on the specified branch should be enough.
Merged:
http://hg.mozilla.org/qa/mozmill-tests/rev/82a8d83fd761 (mozilla-aurora) tag
http://hg.mozilla.org/qa/mozmill-tests/rev/a53018918e5c (mozilla-beta) merge
http://hg.mozilla.org/qa/mozmill-tests/rev/2d973169bc41 (mozilla-beta) tag
http://hg.mozilla.org/qa/mozmill-tests/rev/2c85cec7b97a (default) tag
http://hg.mozilla.org/qa/mozmill-tests/rev/fdde1e2023d5 (mozilla-aurora) merge
http://hg.mozilla.org/qa/mozmill-tests/rev/c7c09c43bf76 (mozilla-aurora) tag

We've merged our branches prior to the actual merges.
Please keep the mozmill-tests trees closed until that is actually done.
This is done.
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in before you can comment on or make changes to this bug.