Firefox/Features/Installers: Difference between revisions

Jump to navigation Jump to search
Line 148: Line 148:
* I did some digging into this and had trouble finding out the usage scenarios associated with these people. Imagine 5.0 has been released. It seems that web developers will probably be running a previous build (4.0.1), a current build (5.0) and maybe a Beta build (6.0b). In this case, all of these would have the app name Firefox.app and they would have to put them in different directories in order to run them side-by-side using different profiles anyhow. We have made a change since FF4 and both the Beta and Release have the same app name. If they are in the same directory, they will replace each other when you install.
* I did some digging into this and had trouble finding out the usage scenarios associated with these people. Imagine 5.0 has been released. It seems that web developers will probably be running a previous build (4.0.1), a current build (5.0) and maybe a Beta build (6.0b). In this case, all of these would have the app name Firefox.app and they would have to put them in different directories in order to run them side-by-side using different profiles anyhow. We have made a change since FF4 and both the Beta and Release have the same app name. If they are in the same directory, they will replace each other when you install.
* In this case, it might be worth changing Aurora to Firefox.app as well but then we lose that "branding" aspect.
* In this case, it might be worth changing Aurora to Firefox.app as well but then we lose that "branding" aspect.
5. Per the requests from Marketing and Product, they want the apps for the channels called...
* Firefox Nightly, Firefox Aurora, Firefox Beta and Firefox.
* Mac: It means adding "Firefox" in front of Nightly and Aurora. The Firefox Beta issue is connected to #3 where we have the same app name for Beta and Release.
* Windows: It means removing the "Mozilla" in front of Firefox for Release and Beta and adding "Firefox" in front of Aurora and Nightly.
* I talked to Gavin about this so I am going to paste the text from the bug were we asked for these changes - "Having unbranded builds include the word "Firefox" (even in just the filename) is a pretty significant change. It means that anyone generating custom builds will get something that references "Firefox" - we've tried hard to avoid that in the past. Our trademark policy doesn't allow the use of "Firefox" at all unless you get explicit permission"
Confirmed users
2,492

edits

Navigation menu