Closed Bug 1269394 Opened 8 years ago Closed 8 years ago

Set up gecko 2.6 (nee 48) branch only on github/mozilla-b2g

Categories

(Developer Services :: General, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: hwine, Assigned: hwine)

References

Details

Due to changes in how the TV branch (FxOS 2.6) will be handled, there is no need for a mercurial version of the gecko branch. Rather, the Repository of Record will be on github.com in the mozilla-b2g organization. It will not be actively updated in the gecko-dev[1] repository, managed by vcs-sync. [1] https://github.com/mozilla/gecko-dev The TV dev team has signed off on this change - it makes their life a lot simpler! \o/
Proposed plan: 1. stop conversion of https://hg.mozilla.org/releases/mozilla-b2g48_v2_6 (set up in 1268117) 2. github fork mozilla/gecko-dev -> mozilla-b2g/gecko-dev (question on name) 3. delete the mercurial repository (set up in bug 1267317) 4. delete b2g48_v2_6 branch from github.com/mozilla/gecko-dev.git & git.mozilla.org/integration/gecko-dev.git Future manual maintenance: - If TV team wants other gecko branches, they follow normal github practice for forks of manually pulling from upstream, and manually pushing to their repo. - If individual devs want b2g48_v2_6 branch in their forks/clone of gecko-dev, they manually add the remote. Open questions: re (2) should repo be called 'gecko-dev' in mozilla-b2g -- or will that cause excessive confusion? re (4) I believe this is preferred to leaving the stale branch in the file, but opinions may vary. gps: comments or concerns?
Flags: needinfo?(gps)
Having it called "gecko-dev" seems a bit confusing. How about "gecko-b2g?" re (4) if you delete the Git branch, commits without a reference will eventually be garbage collected. That feels like the right way to do thing.
Flags: needinfo?(gps)
Repo "retired" on hg.mozilla.org, and removed from web display. New repository of record is https://github.com/mozilla-b2g/gecko-b2g
Assignee: nobody → hwine
Status: NEW → ASSIGNED
all done, afaict.
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.