Closed Bug 909975 Opened 12 years ago Closed 12 years ago

Tracking bug for build and release Fennec 23.0.2

Categories

(Release Engineering :: Release Requests, defect)

x86
Android
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: joduinn, Unassigned)

References

Details

From mobile product meeting this morning, it looks like we'll be asked to generate a Fennec-only dot-release, to fix an mobile-only audio problem for specific hardware partner. Nothing to do yet, but filing bug to track. Also cc-ing bajaja, akeybl, lsblakk. Notes: 1) this will be needed as-soon-as-reasonable, but is *not* a chemspill. Bug#860599 needs to be landed across the branches before this can start. 2) This fennec build should *not* be posted to any of the android stores, to avoid needless churn for Fennec users not-on-this-partner-pre-release-hardware (ie everyone!). It wil be fine to later post to all android stores as part of any later dot-release / security release, but for now, this release build will be handed off by mfinkle to the partner to verify functionality. 3) Users on this release build should get updated, as usual, to the next Fennec release, whenever we do that. 4) We have already shipped FF23.0.1 for desktop, so to avoid confusion, we think its best to call this release FF23.0.2.
I've email Karen/Mark already on the possibility of this given it was the first time I heard of it from John this afternoon. Will loop back with any updates I get.
23.0.2 is fine, we'll use ship-it and given there's no release (other than to FTP) we should consider this pretty low-resource & low-risk.
Whiteboard: kanbanzilla[Ready to work on]
Whiteboard: kanbanzilla[Ready to work on]
Given that we're shipping 24.0 next week, I doubt that this is going to happen...
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
(In reply to Ben Hearsum [:bhearsum] from comment #3) > Given that we're shipping 24.0 next week, I doubt that this is going to > happen... Correct. Although we might be filing a similar bug for a Fx24.0.1 in the future.
You need to log in before you can comment on or make changes to this bug.