Confirmed users
1,041
edits
Firefox/Features/Installers: Difference between revisions
m
→Overview
m (→Overview) |
m (→Overview) |
||
| Line 226: | Line 226: | ||
As I understand the purpose from several discussions starting well over a year ago, we want to increase the number of "regular" users running Aurora and Beta builds where regular is more representative of the majority of Firefox users. If that is the primary goal then we should optimize for that case and the only time we shouldn't optimize for that case is when it prevents power users (developers, web developers, etc.) from being able to use Firefox. | As I understand the purpose from several discussions starting well over a year ago, we want to increase the number of "regular" users running Aurora and Beta builds where regular is more representative of the majority of Firefox users. If that is the primary goal then we should optimize for that case and the only time we shouldn't optimize for that case is when it prevents power users (developers, web developers, etc.) from being able to use Firefox. | ||
Firefox has never supported side by side installations of release builds without the person performing the installation performing additional steps. For example, on Windows existing shortcuts for a release build will be replaced and on Mac the installation requires installing into a location where there isn't already | Firefox has never supported side by side installations of release builds without the person performing the installation performing additional steps. For example, on Windows existing shortcuts for a release build will be replaced and on Mac the installation requires installing into a location where there isn't already a release build installation by dragging the Firefox icon to a location outside of the dmg's user interface. Even with the newly proposed naming this will still be the case. | ||
For the web developer case I believe a better solution should be created that doesn't get in the way of us implementing features like channel changing. Sayer brought this up to me recently and we came up with an outline of how this could be accomplished that addresses the naming issue under discussion as well as the pre-existing naming issue when installing multiple releases. | For the web developer case I believe a better solution should be created that doesn't get in the way of us implementing features like channel changing. Sayer brought this up to me recently and we came up with an outline of how this could be accomplished that addresses the naming issue under discussion as well as the pre-existing naming issue when installing multiple releases. | ||