Thank you - that sounds great! :-)
On 05/08/2014 19:26, John Ford wrote:
I've been thinking of a way to fix this but haven't written the proposal
out. The end result would have all the scripts move into repo managed
git repositories and have the actual B2G.git repository turn into a
script that has enough to bootstrap repo.
I hope to have this written up this week.
John
On Aug 5, 2014, at 9:10 AM, Chris Atlee <[email protected]
<mailto:[email protected]>> wrote:
> On 13:22, Tue, 05 Aug, Ed Morley wrote:
>> The repo mozilla-b2g/B2G is currently not handled by the B2G bumper
>> bot (script that uses a set of templates in the b2g-manifest repo to
>> update the manifests in the gecko repo) - and so:
>> a) It becomes hard for people to land backwards incompatible changes
>> to mozilla-b2g/B2G if they also require changes to repos that _are_
>> tracked by the bumper bot (eg 1047350).
>> b) No commit is displayed on TBPL/treeherder, which makes the root
>> cause of failures due to changes to this repo harder to find (eg bug
>> 1048819).
>>
>> The solution is to add B2G bumper bot support for this repo - which
>> means the B2G build will only use the revision listed in the manifest
>> inside the relevant gecko repository, and not just silently pull master.
>>
>> With this there are two options:
>> 1) Have the B2G bumper bot follow master of mozilla-b2g/B2G for all
>> branches, including mozilla-b2g30_v1_4, ...
>> 2) Create v2.x, v1.x branches on mozilla-b2g/B2G (the same gonk-misc,
>> ...), and have legacy branches such as mozilla-b2g30_v1_4 follow v1.4
>> etc.
>>
>> #2 would be the ideal solution, since it solves both (a) and (b)
>> above, whereas #1 would only solve (b).
>>
>> Are there any objections to doing #2?
>
> There's currently no place to record this branch/revision. B2G is not
> tracked by any of the device manifests, and the current directory
> structure has the B2G checkout being outside of any of the
> repositories tracked by the device manifests.
>
> Where do you propose we track the B2G repo branch/commit?
> _______________________________________________
> dev-b2g mailing list
> [email protected] <mailto:[email protected]>
> https://lists.mozilla.org/listinfo/dev-b2g
_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g
