Closed
Bug 687570
Opened 14 years ago
Closed 14 years ago
New project branch request: WebRTC
Categories
(Release Engineering :: General, defect, P2)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: anant, Assigned: lsblakk)
Details
(Whiteboard: [project branch])
Attachments
(1 file)
|
779 bytes,
patch
|
armenzg
:
review+
lsblakk
:
checked-in+
|
Details | Diff | Splinter Review |
We're working on integrating video conferencing capability from webrtc.org into Firefox and need a project branch to start with.
Project name: webrtc
For builds:
- No builds required. An initial clone of mozilla-central would be appreciated.
Need unittests?
- No tests required.
Need Talos?
- No Talos runs required.
Name of the contact person for this branch who will:
Be doing periodic refreshes from parent
Be contact person for misc setup questions
Decide when to land back project branch onto parent
Decide when to terminate the project branch
- Randell Jesup (jesup@jesup.org)
Timeline:
When should this branch go live?
- As soon as convenient.
Approx expected life span of project branch?
- ~6months-1year
Thanks!
| Assignee | ||
Comment 1•14 years ago
|
||
Hi Anant,
I've added you as "next in line" to the booking schedule for alder which is one of our disposable branches. Since your estimated lifespan is not infinite, the disposable branches are better suited and can be tweaked according to your needs - ie: no tests/talos.
See: https://wiki.mozilla.org/ReleaseEngineering/DisposableProjectBranches#BOOKING_SCHEDULE
Just spoke with philikon in #developers and they are able to hand it off now and grab a different disposable branch later when they resume work. Let me know, in this bug, when your repo is set up and I can land configs to turn off tests/talos when you're ready to start pushing.
| Reporter | ||
Comment 2•14 years ago
|
||
Hey Lukas,
Thanks for taking a look at this - ready to push the repo (easy because we're just starting with a m-c clone) when you are!
Booking alder would make sense, I hope it's not a problem that we might be holding it for a year?
| Assignee | ||
Comment 3•14 years ago
|
||
No problem taking it for as long as you need it - please just put as accurate a start and end date in the schedule. Follow the steps here: https://wiki.mozilla.org/ReleaseEngineering/DisposableProjectBranches#Book_one_of_our_fabulous_.22disposable.22_project_branches to get started. I'll attach a patch for alder with tests/talos disabled.
| Assignee | ||
Comment 4•14 years ago
|
||
Attachment #561187 -
Flags: review?(armenzg)
Updated•14 years ago
|
Attachment #561187 -
Flags: review?(armenzg) → review+
| Assignee | ||
Comment 5•14 years ago
|
||
Comment on attachment 561187 [details] [diff] [review]
turn off talos/tests for alder branch
landed on default: http://hg.mozilla.org/build/buildbot-configs/rev/f687e9cf4ba5
Attachment #561187 -
Flags: checked-in+
| Reporter | ||
Comment 6•14 years ago
|
||
export REPO_PATH=mozilla-central
export TWIG=alder
cd /repo/hg/scripts/
./reset_pp_repo.sh -s /repo/hg/mozilla/$REPO_PATH -r tip -d $TWIG
Could we get a fresh clone of mozilla-central onto alder? The wiki page implied that the above script needed to be executed, but if not, can I just go ahead and check-in?
| Reporter | ||
Comment 7•14 years ago
|
||
Filed bug #687914 for IT to clone m-c onto alder.
| Assignee | ||
Comment 8•14 years ago
|
||
When bug 687914 is closed you should be able to get started, there might be tests/talos until the next reconfig but the patch to turn those off is in default branch and will get enabled soon on the next reconfig which should be at some point this week. Resolving this bug as there is nothing else for me to do here.
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
| Reporter | ||
Comment 9•14 years ago
|
||
IT has finished the import, we're all set. Thanks Lukas!
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•