Confirmed users
1,041
edits
Firefox/Features/Installers: Difference between revisions
→Reasons for using the same install name for release, beta, and aurora
m (→Overview) |
|||
| Line 230: | Line 230: | ||
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. | ||
=== Reasons for using the same install name for release, beta, and aurora === | === Reasons for channel switching and using the same install name for release, beta, and aurora === | ||
* Channel changing is much simpler. When channel switching there are less options to choose from, less steps to perform, and a single user interface for user user to interact with (About window vs. About window, web page, download manager, and installer) when compared to installing. Simplicity is a key point because of the audience we want to attract. | * Channel changing is much simpler. When channel switching there are less options to choose from, less steps to perform, and a single user interface for user user to interact with (About window vs. About window, web page, download manager, and installer) when compared to installing. Simplicity is a key point because of the audience we want to attract. | ||