Closed
Bug 1250994
Opened 9 years ago
Closed 9 years ago
Stop building and testing Android API 9-10 in Firefox 48 Nightly
Categories
(Release Engineering :: General, defect)
Tracking
(fennec48+)
RESOLVED
FIXED
Tracking | Status | |
---|---|---|
fennec | 48+ | --- |
People
(Reporter: rnewman, Assigned: gbrown)
References
Details
I have a patch in Bug 1220184 that removes the mozconfigs.
We should stop running builds and tests in 48 (March 7th onwards), and have this change ride the trains.
jlund, gbrown, this should give you some cause to celebrate. Could you file any additional dependencies?
Flags: needinfo?(jlund)
Comment 1•9 years ago
|
||
wow, \o/
I filed 1250999 with my initial thoughts on strategy. will leave this open to branch off of so gbrown/ateam can file/add any test automation changes required.
Flags: needinfo?(jlund)
Comment 3•9 years ago
|
||
This will impact our testing using Nexus S devices. The immediate effect will be that there will no longer be pulse notifications of builds and tests will no longer be run on the Nexus S devices. At that time, I can either adjust the manifests as the change rides the trains or simply keep them as is and remove them altogether when Firefox 48 is released. Once Firefox 48 is released we will be able to decommission and recycle all of the Nexus S devices.
Flags: needinfo?(bob)
Reporter | ||
Updated•9 years ago
|
Updated•9 years ago
|
Component: Release Automation → General Automation
QA Contact: bhearsum → catlee
Comment 4•9 years ago
|
||
Following up on this now that rnewman is working on other projects. Geoff, I don't see any updates on this bug but I also don't see builds in treeherder anymore - are there more things to do about these builds, or is this done?
Assignee | ||
Comment 5•9 years ago
|
||
There's still activity in bug 1250999. Other than that, I think we're done.
Assignee | ||
Updated•9 years ago
|
Assignee: nobody → gbrown
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Updated•7 years ago
|
Component: General Automation → General
You need to log in
before you can comment on or make changes to this bug.
Description
•