Closed Bug 1350405 Opened 8 years ago Closed 8 years ago

Streamlined stub set Firefox as default browser (impacts Funnelcakes 99 and 100 only)

Categories

(Firefox :: Installer, enhancement)

enhancement
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: RT, Assigned: agashlin)

References

Details

(Whiteboard: [fce-active-legacy])

User Story

The current streamlined stub installer used for funnelcakes 99 and 100 auto sets Firefox as default browser. 
The desired behavior is to not change the default browser setting:
- If Firefox was already installed and set as default then keep Firefox as default browser
- If Firefox was not set as default browser then remain this way

The next Funnelcake test will re-use the streamlined stub installer and we should fix this bug to support the funnelcake so that iterations can happen within Firefox to test the most efficient way to offer users to set Firefox as default. These tests will help define the best approach to fix bug 1272162.
No description provided.
User Story: (updated)
Blocks: 1328445
Assignee: nobody → agashlin
Whiteboard: [fce-active]
Blocks: 1348127
Hi Adam, the onboarding team target for the next funnelcake is to build it on April 7th, can you confirm if this bug would be fixed for this funelcake so they can plan accordingly?
Flags: needinfo?(agashlin)
I'll get an updated patch together (based on the patch for fc 99/100 in bug 1328445 which introduced this bug) by the end of today, if no complications come up.
Flags: needinfo?(agashlin)
Could you clarify what is to happen on April 7? I understand this funnelcake is for 53, but as release for 53 isn't until April 14 that would suggest that any build of 53 on April 7 will be on the beta update channel. Also, as with last time, the stub won't be able to download and install the funnelcake repacks until they are up on bouncer. So a full test with the streamlined stub and repacked full installer won't be possible until they have been tested and built for release separately.
Flags: needinfo?(rtestard)
Hey Adam, I had asked Romain to get all the fixes to the stub installer landed in Oak by April 7th so that RelEng can start building the funnelcakes pointing to the binary by April 10th. I am not an expert on the process, so if this is not correct please let me know and we can coordinate with RelEng on the date that these fixes need to land. NeedInfo'ing Jordan Lund for this purpose.
Flags: needinfo?(rtestard) → needinfo?(jlund)
I'm fine with testing on Oak like we did last time, but we'll land these changes on a branch in mozilla-release for the actual stub installers. That will be possible later on the 10th, which is also when the first 53.0 RC builds will be available and we can create the full installers.
Flags: needinfo?(jlund)
As Nick mentioned, for official release builds sake, we merge beta->release that day and build a release-candidate (build1). We usually QA test that candidate throughout the week and decide if we need a build2(..buildN) before we actually ship on April 18th. I don't think we are releasing or building anything on April 14th. Sounds like we need to have stub and funnelcake patches ready for Mon, 10th and testing can be done on a project branch like oak
Oops, I mentioned the 14th by mistake. I will aim to get the patches on Oak and have builds available before the end of the week.
Hey Adam, Are we still on track to get the patches landed on Oak today?
Flags: needinfo?(agashlin)
Flags: needinfo?(agashlin)
(In reply to Matt Howell [:mhowell] from comment #9) > I pushed the patches to oak earlier today: > https://hg.mozilla.org/projects/oak/pushloghtml?changeset=1e8960c87a20 Great! Thanks for the update. Is there any further action on this bug? Or can we consider this bug fixed?
Flags: needinfo?(mhowell)
The oak builds are just for testing; we should probably leave this open until the patches from bug 1353576 are applied on the actual release branch.
Flags: needinfo?(mhowell)
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Whiteboard: [fce-active] → [fce-active-legacy]
You need to log in before you can comment on or make changes to this bug.