Closed
Bug 507950
Opened 15 years ago
Closed 15 years ago
Add Namoroka branding to mozilla-central
Categories
(Firefox Build System :: General, defect, P1)
Firefox Build System
General
Tracking
(Not tracked)
VERIFIED
FIXED
mozilla3.6a1
People
(Reporter: nthomas, Assigned: reed)
References
()
Details
Attachments
(1 file)
2.87 KB,
patch
|
Gavin
:
review+
|
Details | Diff | Splinter Review |
+++ This bug was initially created as a clone of Bug #439410 +++ mozilla-central still uses Shiretoko for the unofficial branding and should be switched to Namoroka before 3.6a1 is created. We'll switch the mozconfigs to unofficial branding in bug 506401.
Flags: blocking-firefox3.6?
Reporter | ||
Updated•15 years ago
|
Priority: -- → P1
Assignee | ||
Comment 1•15 years ago
|
||
Something like this?
Comment 2•15 years ago
|
||
Comment on attachment 392753 [details] [diff] [review] patch - v1 Looks good! Need a followup to apply the equivalent of http://hg.mozilla.org/releases/mozilla-1.9.1/rev/04eb06993202 on the branch once it exists.
Attachment #392753 -
Flags: review?(gavin.sharp) → review+
Assignee | ||
Comment 3•15 years ago
|
||
http://hg.mozilla.org/mozilla-central/rev/60b03c15a550 When the 1.9.2 branch is created, I'll follow-up.
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 3.6a1
Comment 4•15 years ago
|
||
(In reply to comment #3) > http://hg.mozilla.org/mozilla-central/rev/60b03c15a550 > > When the 1.9.2 branch is created, I'll follow-up. Once the 1.9.2 branch is created, we'll need: * the mozilla-192 branch be "Namoroka" * change mozilla-central to be whatever is the next projectname after "Namoroka".
Comment 5•15 years ago
|
||
Given that mozilla-central will remain "trunk" for the forseeable future, I think we should leave it as "Minefield". We'll be creating a mozilla-1.9.3 branch, or whatever when we get ready to ship the thing after Namaroka.
Comment 6•15 years ago
|
||
I understood John's comment to mean "change unofficial branding on mozilla-central to be whatever the next code name is", rather than "change the default branding away from the nightly/minefield" like we do on branches. Since we don't know what the next one is going to be called, and since we don't plan on branching again in the near future, I don't think we actually need to worry about that :)
Reporter | ||
Updated•15 years ago
|
Flags: blocking-firefox3.6?
Comment 7•15 years ago
|
||
(In reply to comment #4) > Once the 1.9.2 branch is created, we'll need: > * the mozilla-192 branch be "Namoroka" Do we already have a bug for that? It's a bit confusing to have two different versions of Minefield (1.9.2 and trunk).
Comment 8•15 years ago
|
||
(In reply to comment #7) > (In reply to comment #4) > > Once the 1.9.2 branch is created, we'll need: > > * the mozilla-192 branch be "Namoroka" > > Do we already have a bug for that? It's a bit confusing to have two different > versions of Minefield (1.9.2 and trunk). Just filed bug 510497
Comment 9•15 years ago
|
||
Verified with Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2a1) Gecko/20090806 Namoroka/3.6a1 ID:20090806155510
Status: RESOLVED → VERIFIED
Updated•5 years ago
|
Component: Build Config → General
Product: Firefox → Firefox Build System
Updated•5 years ago
|
Target Milestone: Firefox 3.6a1 → mozilla3.6a1
You need to log in
before you can comment on or make changes to this bug.
Description
•