Add Namoroka branding to mozilla-central

VERIFIED FIXED in Firefox 3.6a1

Status

()

P1
normal
VERIFIED FIXED
9 years ago
8 years ago

People

(Reporter: nthomas, Assigned: reed)

Tracking

Trunk
Firefox 3.6a1
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

Attachments

(1 attachment)

(Reporter)

Description

9 years ago
+++ 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

9 years ago
Blocks: 506401
(Reporter)

Updated

9 years ago
Priority: -- → P1
(Assignee)

Comment 1

9 years ago
Created attachment 392753 [details] [diff] [review]
patch - v1

Something like this?
Assignee: nobody → reed
Status: NEW → ASSIGNED
Attachment #392753 - Flags: review?(gavin.sharp)
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

9 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
Last Resolved: 9 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 3.6a1
(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".
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.
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

9 years ago
Flags: blocking-firefox3.6?
(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).
(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
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
You need to log in before you can comment on or make changes to this bug.