Closed Bug 910372 Opened 8 years ago Closed 8 years ago

B2G Product is not shown


(Socorro :: Webapp, task)

Gonk (Firefox OS)
Not set


(Not tracked)



(Reporter: nhirata, Unassigned)



(Keywords: qablocker, Whiteboard: [stage][prod])


(3 files)

1. go to
2. click on products

Expected: going to the website would show B2G results, not Firefox Desktop.  The menu is missing B2G
Actual: B2G is missing in the menu, the data is not shown
I'm pretty sure it's just that the date for 18.0 being an "active" version has expired, so we have no "active" versions listed, and that makes it missing.
Severity: normal → blocker
Whiteboard: [stage][prod]
I think that's an amusing bug, because the numbers on that page are for Firefox.

The last B2G aged out yesterday. The scraper isn't finding anything (something changed in releng). If we were still scraping, we'd only be seeing crashes from the releng produced images.

What do you expect to see when you go to B2G?
Depends on: 910385
I expect to see the B2G headers and also be able to do a search on B2G.  Currently it shows only Firefox information. B2G isn't even a product option in the search.
The crash reports themselves are still useful.
We should set 18.0 not to time out yet, it will be alive for a lot longer, esp. as we are shipping another major release off 18.0 in October and AFAIK are committed to maintaining that for at least half a year.

Given that, let's manually set the end date for 18.0 to 2014-04-30 - with that, B2G will be visible again and searches will work. We know we have to do some more stuff for it anyhow (and actual end-user releases aren't caught by FTP scraper as we also know).
We extended the life of the last b2g build for 1 month. Bug 910385 is filed to fix the ftp scraper but isn't necessarily blocking. If you check the UI b2g is back as a product.
Closed: 8 years ago
No longer depends on: 910385
Resolution: --- → FIXED
Attached image qa - verified on prod
QA verified on prod - b2g crashes are searchable via the advanced query page.
Blocks: 915257
You need to log in before you can comment on or make changes to this bug.