405463 - Inform users on install that they are part of the Beta Program

Status: RESOLVED WONTFIX

(Firefox :: Installer, enhancement, P4)

Description

[Carsten Book [:Tomcat]]

Currently we have the situation that users are not informed on install that they are part of the Firefox Beta Program. You only notice this with RC Updates (for Firefox 2.x) and with a modified Startup page.

When you install a Firefox 3 Beta 1 as example you get no notice that this beta program is also valid for later Firefox 3 Security Releases (like Firefox 3.0.0.1) and does not end with the Firefox 3 Release.

Maybe we could add a notice to the installer ("You are about to install a Firefox Beta Version and you are now part of the Firefox Beta Community [maybe with a included hardcoded link to a page what "beta program" mean), or with a Checkbox in the Installer like:

default [x][yes i want to be part of the Firefox Beta Program]-> "beta" update channel

and if they uncheck this the update channel is "release"

This would help to get more awareness of the Firefox Beta Program and also help to get more feedback from beta users.

Comment 1

[Robert Strong (they/them - no direct email)]

All of the brand long name branding includes Beta 1 which I personally believe is above and beyond the call of duty here.

Comment 2

[Daniel Veditz [:dveditz]]

I believe Carsten's point is not that the installed release is a beta (which, yes, it says "BETA" right in the title) but that the user is now permanently signed up for all future betas on that branch, both pre-release (expected) and for security updates post-release (probably not expected).

Comment 3

[Daniel Veditz [:dveditz]]

This doesn't necessarily require product changes, we might decide that the post-install "what's new" page for the beta is sufficient in telling people 1) you're in the beta and 2) if you don't want to be go reinstall a release copy.

The current pages attempt to convey that information, but it's buried in a lot of text that encourages non-reading. Worse, it's not localized.

Comment 4

[Robert Strong (they/them - no direct email)]

The opt-in part of comment #0 is what concerns me. If text is provided to replace existing text and that is managed during beta builds then this is reasonable afaic though it is another difference between nightly / beta / release builds that could bite us as similar changes have in the past.

Adding this to the "What's new" page is by far the safest.

Comment 5

[Mike Connor [:mconnor]]

Not a blocker, but wanted.

Comment 6

[Jesse Ruderman]

I think it would be better to allow all users, not just users who have downloaded a beta, to decide whether they want beta updates.  We need more users testing security updates to avoid shipping with regressions, and letting users opt into betas of security updates seems like a sane way to do that.

See also bug 266994.

Comment 7

[Robert Strong (they/them - no direct email)]

Making this a part of the installer is IMO not the way to go. First, this will limit it to just windows. Second, we don't have a good way for the installer to know what channels are available and to select one accordingly. I personally think this should be an additional feature provided by software update and configurable via the preferences.

Comment 8

[Robert Strong (they/them - no direct email)]

btw: comment #7 is in regards to the additional functionality detailed in the comments and not for the basic request as described in the summary of "Inform users on install that they are part of the Beta Program"

Filed bug 410639 for the ability to change update channels as mentioned in comment #0

Comment 9

[Robert Strong (they/them - no direct email)]

Tomcat, what do you think of just making this part of the first run page instead? Then it would apply to all platforms and it would be much easier to customize / maintain / etc.

Comment 10

[Robert Strong (they/them - no direct email)]

I really don't think this should be added to the installer for the reasons I've stated along with that I will be trying to simplify the installer in the near future and think a much better solution would be to have the browser inform the user on first run when running a beta. Resolving->wontfix.