Bug 507950 - Add Namoroka branding to mozilla-central
Description From Nick Thomas [:nthomas] 2009-08-02 18:43:55 PDT
+++ 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.
------- Comment #1 From Reed Loden [:reed] (on indefinite leave from the Mozilla project) 2009-08-05 11:00:59 PDT -------
Created an attachment (id=392753) [details]
patch - v1
Something like this?
------- Comment #2 From Gavin Sharp 2009-08-05 11:16:17 PDT -------
(From update of attachment 392753 [details])
Looks good!
Need a followup to apply the equivalent of
http://hg.mozilla.org/releases/mozilla- ... eb06993202 on the branch
once it exists.
------- Comment #3 From Reed Loden [:reed] (on indefinite leave from the Mozilla project) 2009-08-05 11:27:33 PDT -------
http://hg.mozilla.org/mozilla-central/rev/60b03c15a550When the 1.9.2 branch is created, I'll follow-up.
------- Comment #4 From John O'Duinn [:joduinn] 2009-08-05 14:23:29 PDT -------
(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 From Ben Hearsum [:bhearsum] 2009-08-06 05:30:39 PDT -------
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 From Gavin Sharp 2009-08-06 19:27:17 PDT -------
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