Closed Bug 543564 Opened 16 years ago Closed 16 years ago

Change branding to something other than "Namoroka" for 1.9.3 alpha1 release

Categories

(Firefox Build System :: General, defect, P1)

defect

Tracking

(blocking2.0 alpha1+)

RESOLVED FIXED
mozilla3.7a1
Tracking Status
blocking2.0 --- alpha1+

People

(Reporter: dbaron, Assigned: dbaron)

Details

Attachments

(1 file, 1 obsolete file)

We don't want to ship 1.9.3 alpha 1 branded as Namoroka (which is the current state of unofficial branding on mozilla-central), although I believe there's still ongoing debate as to what it should ship as. See bug 507950 and bug 439410 for the last two branding changes that would be equivalent to this patch. Since there's (so far) no decision as to what branding we *should* have, my strawman proposal is as follows: * replace "Namoroka" branding with "Gecko" * keep 3.7a1 as the application version number (I'm afraid doing anything else could confuse the updater) * don't send any "extra" bit in the User-Agent string at all I've heard rumors shaver might have a better proposal, but I don't yet know what it is.
That said, I would prefer that somebody (shaver / beltzner) just come up with a park name.
Beltzner is not around this week. How about picking "Mozilla Preview Release" and sticking up with that for similar future milestones as well?
I'll figure this out by the end of tomorrow.
Assignee: nobody → shaver
Sorry, off by a day! "Mozilla Developer Preview 3.7a1" carries the pragmatism day. I don't really want "3.7" in there, but I found enough places looking yesterday that seem to (probably) depend on some ordering relative to 3.6 that I don't want to mess with it unless we change the main app name/UUID, which is insanity.
Assignee: shaver → nobody
Attached patch patchSplinter Review
Patch to switch from "Namoroka" to "Mozilla Developer Preview" and from http://www.mozilla.org/projects/namoroka/ to http://www.mozilla.org/projects/devpreview/ (for lack of any better ideas).
Attachment #425315 - Flags: review?(gavin.sharp)
Re comment #1, if the preference is to come up with a park name how about Ubajara park in Brazil? http://en.wikipedia.org/wiki/Ubajara_National_Park I don't mean to usurp the park naming rights, but it seems like Brazil has a great Mozilla community and it's South America's turn.
Though, as far as I can tell, we don't use releaseBaseURL anymore; we use app.releaseNotesURL instead.
Attachment #425315 - Flags: review?(gavin.sharp) → review+
Comment on attachment 425315 [details] [diff] [review] patch >diff --git a/browser/branding/unofficial/configure.sh b/browser/branding/unofficial/configure.sh >-MOZ_APP_DISPLAYNAME="Namoroka" >+MOZ_APP_DISPLAYNAME="Mozilla Developer Preview" The spaces here cause build problems. Since this isn't particularly user-visible (primarily used for updater strings and the package name on Mac), I think we should go with MozillaDeveloperPreview, which matches what we did for Bon Echo and Gran Paradiso. r=me with that change.
http://hg.mozilla.org/mozilla-central/rev/b6f7a0dbbfef (I think I have the patch to make it work with spaces, but probably not worth messing with.)
Assignee: nobody → dbaron
Status: NEW → RESOLVED
Closed: 16 years ago
Priority: -- → P1
Resolution: --- → FIXED
(In reply to comment #5) > Does http://www.mozilla.org/projects/devpreview/ seem like an ok URL base? > (Compare http://www.mozilla.org/projects/namoroka/ , > http://www.mozilla.org/projects/minefield/ , etc.) I suppose one downside of this is that if we reuse "Developer Preview" in the future (4.0, 5.0, etc), then there's no historical version of the page for people to reference, and old builds would still go there. OTOH, one upside is that it can become a canonical address for developer previews, and this hasn't been a problem for Minefield. Just thought I'd mention this, even though it seems fine to me.
If you doesn't have ideas, you can send a post in dev.planning and ask people to find out what they think about it. Mozilla Developer Preview is very long name,, so you can use -> http://en.wikipedia.org/wiki/Forillon_National_Park
patch v2
The discussion is done, but thanks for the suggestion. The naming is pretty inconsequential, so let's just let this bug rest in peace.
Attachment #425431 - Attachment is obsolete: true
Sorry to say this so late, but it's too bad that we ship a Firefox UI and call it by a name that implies this would be all "Mozilla" has to offer as a preview. We should really try to not make "Mozilla" == "Firefox"...
This preview is very much about the web developer platform, which is part of all Mozilla browsers, so I think it's appropriate -- in fact, it was part of my reasoning behind choosing it. There weren't any Firefox app features that were targeted at this milestone; the closest was OOPP, which is really a platform feature with a bit of primitive app UI on top. I don't think we should pretend that Firefox *isn't* part of, or representative of, Mozilla. This is the best way to get the Mozilla web platform in front of web developers and others, for the benefit of all Mozilla projects, and indeed developers "affiliated" with all Mozilla projects contributed to the improvements there.
Shaver, I see that, but even the Thunderbird or Calendar UI is Mozilla code. In any case, it's too late to have this discussion for this preview anyhow, so let's just end the talk here, even though the name is suboptimal.
You know that the Mozilla Developer Preview is very long name to fit in some of the windows? Please let the codename will be a national park (to give more interest). It is not yet too late.
Component: Build Config → General
Product: Firefox → Firefox Build System
Target Milestone: Firefox 3.7a1 → mozilla3.7a1
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: