Closed Bug 340862 Opened 20 years ago Closed 20 years ago

push .MAR files for updating Bon Echo Alpha 2 users to Bon Echo Alpha 3

Categories

(Release Engineering :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: beltzner, Unassigned)

References

()

Details

See URL for thread in d-a-f, but the summary is: - more people testing the most recent release is better - the AUS bits (generated by rhelmer at time of A3 ship) are ready and waiting - unless there's a compelling reason not to, we should update people on the beta channel to Alpha 3
I don't think the .MAR files generated will install talkback if it's not already installed.. I am guessing this is due to the fact that talkback is purposely installed on only a small percentage of win32 installs.
(In reply to comment #1) > I don't think the .MAR files generated will install talkback if it's not > already installed.. I am guessing this is due to the fact that talkback is > purposely installed on only a small percentage of win32 installs. > Yup, that is by design. Anything in the "extensions/" folder is viewed as optional by the update process. Users choose talkback (or have it chosen for them) at install time only.
Actually, that has changed with the new installer: we now install talkback for everyone, but only enable it for some percentage of users (currently 75%, will be 10% for final releases).
With the exception of users that explicitly don't install talkback when choosing an Advanced install. I would like to remove the option to not install talkback in the advanced install for release builds if / when DOMi is no longer included in the installer.
As I've said several times and we've agreed in Bon Echo meetings - we will start the update process when we go from b1->b2. :-)
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → WONTFIX
All I saw in the status meeting notes about a3 updates was from http://wiki.mozilla.org/Firefox2/StatusMeetings/2006-05-30, which said "waiting for preed before we ship the AUS bits (should we announce that?)". I wasn't at that meeting, so I didn't hear the reasoning for why we wouldn't ship them at all, which is not to say that it wasn't entirely excellent reasoning. Having that reasoning explained here or in the d-a-f thread or the meeting notes would probably get everyone in the same place. (Given that we have the MARs already in place, it seems like a small amount of effort to push the XML descriptors, and get more eyes on a3, but I'm just repeating myself now. Apologies.)
Assignee: build → nobody
QA Contact: mozpreed → build
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.