821898 - switch manifests to git.mozilla.org for remaining b2g repos

Status: RESOLVED FIXED

(Firefox OS Graveyard :: GonkIntegration, defect)

Description

[Hal Wine [:hwine] use NI!]

We now have the rest of the repositories being mirrored to git.m.o (bug 815846). Now the manifests can be updated to reference them (similar to bug 813710 for gecko.git & gaia.git).

Per bug 816235 comment #2, I believe this needs to be a C3 deliverable, so nom for bb.

Comment 1

[Andrew Overholt [:overholt]]

Hal, this is something you're going to do, right?

Comment 2

[Hal Wine [:hwine] use NI!]

No - this would be done by someone on the b2g build team. Moving to :jhford

Comment 3

[John Ford [:jhford] CET/CEST Berlin Time]

Hal, can you confirm that the repos are fully set up and are syncing the latest content of the upstream repos?

Comment 4

[Hal Wine [:hwine] use NI!]

John - yes - no problems with that - I just resolved the bug to make that clear

Comment 5

[Andrew Overholt [:overholt]]

(In reply to Hal Wine [:hwine] from comment #4)
> John - yes - no problems with that - I just resolved the bug to make that
> clear

So should we close this bug?

Comment 6

[Hal Wine [:hwine] use NI!]

(In reply to Andrew Overholt [:overholt] from comment #5)
> (In reply to Hal Wine [:hwine] from comment #4)
> > John - yes - no problems with that - I just resolved [bug 815846] to make that
> > clear
> 
> So should we close this bug?

Only after John lands the changes. by "resolved the bug", I meant bug 815846 - my apologies for the confusion.

Comment 7

[Dietrich Ayala (:dietrich)]

Per conversation with akeybl & joduinn, unblocking basecamp on this. The blocking-basecamp flags are not being used for build/infra work.

Comment 8

[Hal Wine [:hwine] use NI!]

Per email thread, this is blocking release. Re nominating

Comment 9

[JP Rosevear [:jpr]]

We actually have been using bb+ for release blockers that actually stop us from handing over to partners.

Comment 10

[Andrew Overholt [:overholt]]

John, what's the status here?

Comment 11

[John Ford [:jhford] CET/CEST Berlin Time]

(In reply to Andrew Overholt [:overholt] from comment #10)
> John, what's the status here?


I'm doing the work over in

https://github.com/mozilla-b2g/b2g-manifest/pull/35

The first attempt of using an xml parser/serializer wasn't accepted, so I deleted that code and have done the changes to the required manifests by hand.  I'm waiting on mwu to take a look at the manifest changes, and if they are satisfactory, I need to land similar changes on the nightly branch (doing that is pretty quick).

Comment 12

[Andrew Overholt [:overholt]]

(In reply to John Ford [:jhford] from comment #11)
> (In reply to Andrew Overholt [:overholt] from comment #10)
> > John, what's the status here?
> 
> 
> I'm doing the work over in
> 
> https://github.com/mozilla-b2g/b2g-manifest/pull/35

Cool.

> I'm waiting on mwu to take a look at the manifest changes,

He's away for a bit.  Can we find someone else?  Maybe cjones?

Comment 13

[Andrew Overholt [:overholt]]

During triage yesterday we discussed with Chris Lee how this doesn't have to happen before the v1 cutoff so let's get it off that list.  Obviously if we're wrong about that please let us know :)

Comment 14

[Hal Wine [:hwine] use NI!]

Need it changed back, please. Including relevant parts of the email thread cited in comment #8 below. See also bug 816235 comment #2 for partner request this be done by end of Dec (cited in comment #0)

Chris Lee: key point is these repositories are part of the deliverable, as the project can not be build without these.

-------- Original Message --------
Subject: 	Fwd: [Bug 821898] switch manifests to git.mozilla.org for remaining b2g repos
Date: 	Fri, 28 Dec 2012 13:56:45 -0800
From: 	Hal Wine <[e-mail]>
To: 	Dietrich Ayala <[e-mail]>
CC: 	joduinn <[e-mail]>, Alex Keybl <[e-mail]>


Dietrich,

I agree build & infr bugs shouldn't block release - however this bug
actually affects the release bits (manifest content) shipped to
partners

If this work is NOT done, Mozilla will be "on the hook" for maintaining
those repos on github for the contract duration. (Including escalation
support during outages, which is why we have moved these and gecko &
gaia to git.m.o already.)

Please reset this as blocking basecamp.

--Hal

-------- Original Message --------
Subject: 	Re: Fwd: [Bug 821898] switch manifests to git.mozilla.org for remaining b2g repos
Date: 	Fri, 28 Dec 2012 14:49:43 -0800
From: 	John O'Duinn <[e-mail]>
Reply-To: 	[e-mail]
To: 	Hal Wine <[e-mail]>, Dietrich Ayala <[e-mail]>, Alex Keybl <[e-mail]>


hi Dietrich/akeybl;

+1 to what Hal said. We need this manifest change landed before the 
15th, or else it has consequences for Mozilla's ongoing support. 
Re-applying the "blocking-basecamp" flag asap, will help make sure devs 
prioritize landing that change in time. This is important, and we're 
happy to help explain in more detail if needed.

tc
John.

Comment 15

[Andrew Overholt [:overholt]]

Reset.

Comment 16

[Hal Wine [:hwine] use NI!]

Update:
 - the manifest changes have been applied to the master branch (comment #11)
 - jhford will produce a 2nd pull request for to merge the change to the nightly branch, which will close this bug

Per discussions, the _only_ changes that are blocking basecamp are for the platforms we deliver on Jan 15 - work on any other platform manifest can be deferred to tef+

Comment 17

[Andreas Gal :gal]

Our manifests are for reference purposes only. Our hardware partners are using their own manifests, and have switched to g.m.o a while back. This bug doesn't block.

Comment 18

[Chris AtLee [:catlee]]

What's the status here?

Comment 19

[John Ford [:jhford] CET/CEST Berlin Time]

This work was done a while ago as a PR in the b2g-manifest repository.