The upcoming Firefox and Thunderbird 1.5 beta release will need an update channel of 'beta' rather than 'default' or 'nightly' (whichever is included by default) in order to address that audience as we intend to. Select the best way to insert 'beta' in place of 'default'/'nightly' in built packages (unpack, swap the channel value, repack). There will be many packages - one set per 30+ locales. An alternative is to build from scratch just for the beta, though this is less desirable. If no solution is found in time, our workaround is that the channel be set in CVS to 'beta' for a couple of build cycles. The downside is that nightly testers may most likely be updated to one of these builds which would then not be updated again until we set the bulk of our beta audience to be updated.
Do we want users who download Firefox 1.5 Beta to get betas of future versions of Firefox, such as Firefox 2.0 Beta, or should they get back on the normal channel once they are upgraded to Firefox 1.5?
(In reply to comment #1) > Do we want users who download Firefox 1.5 Beta to get betas of future versions > of Firefox, such as Firefox 2.0 Beta, or should they get back on the normal > channel once they are upgraded to Firefox 1.5? We don't have a solid answer on this right now but that's OK. I've heard good points for both sides. Since we can tune AUS2 to update Firefox 1.5 Beta-based installs to any new build we can proceed as normal and address the question later as we build consensus either way.
1.5 beta is long gone, so I think this can be closed...
Status: NEW → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.