The default bug view has changed. See this FAQ.

Create FF5.0b1 ahead-of-schedule to allow testing of aurora <--> beta channel switching

RESOLVED FIXED

Status

Release Engineering
Other
RESOLVED FIXED
6 years ago
4 years ago

People

(Reporter: joduinn, Assigned: lsblakk)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(3 attachments, 8 obsolete attachments)

7.37 KB, patch
catlee
: review+
lsblakk
: checked-in+
Details | Diff | Splinter Review
12.76 KB, patch
catlee
: review+
lsblakk
: checked-in+
Details | Diff | Splinter Review
1.77 KB, patch
catlee
: review+
Details | Diff | Splinter Review
To verify that all the channel switching is setup correctly, we plan to:

* land changes to AUS to support channel changing to "latest"
* overwrite the contents of the still-unused mozilla-beta repo (and the corresponding l10n repos) with the tip of mozilla-aurora (and the corresponding l10n repos).
* generate a build in mozilla-beta as if it was a real beta (signing, branding, etc).
* ask aurora users to try switching channels, verify that they are on beta build, and to then switch back to aurora.

NOTE:
* We need to be careful that this build on the beta channel is NOT picked up by all the beta users.
* We need to be quiet about this since it's not beta quality code - its an early copy of aurora quality code. Doing this mainly for internal testing and dev purposes.
* If many users switch aurora->beta and then *stay* on that "fake" beta, we may need to generate custom snippets to update them to a real beta at a later time.


(a lot going on, so if I missed anything, please add/edit!)
(In reply to comment #1)
> * If many users switch aurora->beta and then *stay* on that "fake" beta, we may
> need to generate custom snippets to update them to a real beta at a later time.

To prevent painting ourselves into a corner, here's a change of plan:

* land changes to AUS to support channel changing to "latest" (bug#648087)
* overwrite the contents of the still-unused mozilla-beta repo (and the
corresponding l10n repos) with the tip of mozilla-aurora (and the corresponding
l10n repos).
* generate FF5.0beta1 in mozilla-beta as a real beta (signing, branding,
etc).
* ask aurora users to try switching channels, verify that they are on beta
build, and to then switch back to aurora. 
* Press/blogs to cover that:
** this FF5.0beta1 beta is really aurora-quality functionality to test new process as we change to faster release cadence. 
** on build day, the functionality of FF5.0beta1 is identical to aurora at first, but over time, as aurora does new nightly builds, this specific FF5.0beta1 will be "older" then aurora. This is expected and temporary.

* On 17may, when aurora->beta happens, we will generate FF5.0beta2. Any users who are still on FF5.0beta1 will be offered updates to FF5.0beta2.
Summary: Create "fake beta" build to allow testing of aurora <--> beta channel switching → Create FF5.0beta1 ahead-of-schedule to allow testing of aurora <--> beta channel switching
mayumi: I just talked with legneato and he's also fine with this plan.
(Assignee)

Comment 3

6 years ago
Created attachment 528328 [details] [diff] [review]
5.0b1 build1 configs

not sure if we want to email vendors for this one - also need to check about verifyConfigs using the 2.0 ones
Attachment #528328 - Flags: review?(catlee)
(Assignee)

Updated

6 years ago
Depends on: 652858
(Assignee)

Comment 4

6 years ago
Created attachment 528346 [details] [diff] [review]
5.0b1 build1 configs
Attachment #528328 - Attachment is obsolete: true
Attachment #528328 - Flags: review?(catlee)
Attachment #528346 - Flags: feedback?(catlee)
(Assignee)

Comment 5

6 years ago
Created attachment 528358 [details] [diff] [review]
5.0b1 build1 configs with default l10n changesets
Attachment #528346 - Attachment is obsolete: true
Attachment #528346 - Flags: feedback?(catlee)
Attachment #528358 - Flags: review?(catlee)
(In reply to comment #3)
> Created attachment 528328 [details] [diff] [review]
> 5.0b1 build1 configs
> 
> not sure if we want to email vendors for this one - also need to check about
> verifyConfigs using the 2.0 ones

No harm to emailing vendors on this one, afaict.
Comment on attachment 528358 [details] [diff] [review]
5.0b1 build1 configs with default l10n changesets

Looks good. Let's set skip_updates for now, since we're going to have to do them by hand anyway.
Attachment #528358 - Flags: review?(catlee) → review+
(Assignee)

Comment 8

6 years ago
Created attachment 528473 [details] [diff] [review]
sample update config files (if we did a 5.0b0)
Attachment #528473 - Flags: feedback?(catlee)
(Assignee)

Comment 9

6 years ago
Created attachment 528475 [details] [diff] [review]
5.0b1 build1 configs with default l10n changesets and skip_updates = True

Added in missing locales that were in mozilla-aurora and not in mozilla-central. Also set 'skip_updates' to True
Attachment #528358 - Attachment is obsolete: true

Updated

6 years ago
Summary: Create FF5.0beta1 ahead-of-schedule to allow testing of aurora <--> beta channel switching → Create FF5.0b1 ahead-of-schedule to allow testing of aurora <--> beta channel switching
Created attachment 528655 [details] [diff] [review]
5.0b1 build1 configs with default l10n changesets and skip_updates = True and no l10n_platforms

So I'm leaving in the creation of the l10n_changesets for beta since we'll want that file for the next beta build anyway. Also setting l10n_platforms to () and renaming the verify config files to 'mozBeta' for now, though with skip_updates this won't be used yet.
Attachment #528475 - Attachment is obsolete: true
Attachment #528655 - Flags: review?(catlee)

Comment 11

6 years ago
Comment on attachment 528655 [details] [diff] [review]
5.0b1 build1 configs with default l10n changesets and skip_updates = True and no l10n_platforms

I like the design on how to work around doing l10n for this one, but can you not change the sign-off source stamps? The new values don't really carry any value, I think, and the diff against the 4.0.x stuff might be good to have.
Created attachment 528665 [details] [diff] [review]
5.0b1 build1 configs, no l10n repo changes just new file

updated to the tip changeset of mozilla-aurora (we will merge into mozilla-beta) since it has some backout/bustage fixes we probably want in this build
Attachment #528655 - Attachment is obsolete: true
Attachment #528655 - Flags: review?(catlee)
Attachment #528665 - Flags: review?(catlee)
Created attachment 528679 [details] [diff] [review]
final? configs for 5.0b1 with no l10n
Attachment #528665 - Attachment is obsolete: true
Attachment #528665 - Flags: review?(catlee)
Attachment #528679 - Flags: review?(catlee)
Created attachment 528681 [details] [diff] [review]
update configs for 5.0b1
Attachment #528473 - Attachment is obsolete: true
Attachment #528473 - Flags: feedback?(catlee)
Attachment #528681 - Flags: review?(catlee)

Updated

6 years ago
Attachment #528679 - Flags: review?(catlee) → review+

Updated

6 years ago
Attachment #528681 - Flags: review?(catlee) → review+
Blocks: 651982
Created attachment 528927 [details] [diff] [review]
major update configs for updating to 5.0b1
Attachment #528927 - Flags: review?(catlee)
Comment on attachment 528681 [details] [diff] [review]
update configs for 5.0b1

http://hg.mozilla.org/build/tools/rev/ca1b4fbe24fe
Attachment #528681 - Flags: checked-in+
Comment on attachment 528679 [details] [diff] [review]
final? configs for 5.0b1 with no l10n

http://hg.mozilla.org/build/buildbot-configs/rev/1971f8c431ac
Attachment #528679 - Flags: checked-in+
Created attachment 528929 [details] [diff] [review]
major update configs for updating to 5.0b1 with 64bit platforms included
Attachment #528927 - Attachment is obsolete: true
Attachment #528927 - Flags: review?(catlee)
Attachment #528929 - Flags: review?(catlee)

Updated

6 years ago
Attachment #528927 - Flags: review+

Updated

6 years ago
Attachment #528929 - Flags: review?(catlee) → review+
Depends on: 654572

Updated

6 years ago
No longer depends on: 654572
This release is out in the wild now.
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.