Closed Bug 1056003 Opened 10 years ago Closed 10 years ago

Please create hg.m.o repo for b2g 2.0m

Categories

(Developer Services :: Mercurial: hg.mozilla.org, defect)

Product:
Developer Services
Component:
Mercurial: hg.mozilla.org
Platform:
x86_64
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: seinlin, Assigned: fubar)

References

Details

Please create the following mercurial repository:

releases/mozilla-b2g32_v2_0m
   cloned from releases/mozilla-b2g32_v2_0
   same permissions as mozilla-b2g32_v2_0
   same hooks as mozilla-b2g32_v2_0
hwine: r?
Assignee: server-ops-webops → klibby
Flags: needinfo?(hwine)
This branch will be specific for Woodduck.
Kai-Zhen Li: branches for b2g are done by the release team, as there is much work outside of the repositiories themselves to make them useful. Please see:
  https://wiki.mozilla.org/ReleaseEngineering/RepositoryCreationRequest

I suspect there is some coordination needed as the new groups spin up -- holding off on approval until we can get in front of any needed changes (should be just a day or two delay max).
Component: WebOps: Source Control → Repos and Hooks
Product: Infrastructure & Operations → Release Engineering
QA Contact: nmaul → hwine
Hwine, Thanks! let's wait the approval.
(In reply to Hal Wine [:hwine] (use needinfo) from comment #3)
> Kai-Zhen Li: branches for b2g are done by the release team, as there is much
> work outside of the repositiories themselves to make them useful. Please see:
>   https://wiki.mozilla.org/ReleaseEngineering/RepositoryCreationRequest
> 
> I suspect there is some coordination needed as the new groups spin up --
> holding off on approval until we can get in front of any needed changes
> (should be just a day or two delay max).

Hi, Hal, any updates? Thanks.
Well, looks like coordination is going to take a bit. 

Let's move ahead with getting you what you need.

Where do you want the branch to be from? tip of mozilla-b2g32_v2_0?

Once I have that, we can get you a repository where developers can commit.

To have any builds, you will need to file bugs requesting that with Release Engineering.
Flags: needinfo?(hwine)
(In reply to Hal Wine [:hwine] (use needinfo) from comment #6)
> Well, looks like coordination is going to take a bit. 
> 
> Let's move ahead with getting you what you need.
> 
> Where do you want the branch to be from? tip of mozilla-b2g32_v2_0?

Whoops, already in comment #0 -- okay to go, :klibby

ni: khu to open the bug with the build requests
Flags: needinfo?(klibby)
Flags: needinfo?(khu)
Jenny, can you follow up this topic? Thanks.
Flags: needinfo?(khu) → needinfo?(jeliu)
Repo all set. http://hg.mozilla.org/releases/mozilla-b2g32_v2_0m/
Flags: needinfo?(klibby)
Depends on: Woodduck
Kendall, Thanks! Will this branch mirror to http://git.mozilla.org/?p=releases/gecko.git automatically?
Flags: needinfo?(klibby)
No, Releng handles that afaik.
Flags: needinfo?(klibby) → needinfo?(hwine)
(In reply to Kai-Zhen Li from comment #10)
> Kendall, Thanks! Will this branch mirror to
> http://git.mozilla.org/?p=releases/gecko.git automatically?

There's an email thread on the mirroring -- I'll forward it to you so everyone is on the same page
Flags: needinfo?(hwine)
this work is done, follow on work covered in bugs.
Blocks: 1062028
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Product: Release Engineering → Developer Services
Clear ni for Jenny.
Flags: needinfo?(jeliu)
You need to log in before you can comment on or make changes to this bug.