I was talking with Ryan (cc'd) about this. He says all the active versions for FennecAndroid are wrong and it's doing more harm than good. We talked about the circumstances which I sort of cover in the previous comment. He pointed out that it's likely the version information will always be wrong. That's probably true and frustrating.
He pointed out maybe we should force all products to update product-details and pull version data from there. I don't know where that data comes from, so I'd need to look into that. It'd be nice if product-details had a single schema--they've got multiple ones and it seems like a dumping ground at the moment. For example, these two are complete different:
I think getting releng and everyone else to establish a single schema and switch all products to publishing that information will take a long time, so we need a short-term fix that isn't automatically generated.
The short-term fix has to have these properties:
- The information source has to be maintained by other people--not me.
- The information source can't be maintained in the webapp. To add this to the webapp is a ton of work: adding a new group, new permissions, web views, tests, tables, process for requesting permissions, granting permissions, rescinding permissions, plus the ongoing maintenance of handling grant requests. That's a lot of up-front and ongoing work. I don't want to do that.
- This has to support all the products that Socorro supports and be easy to add new products.
I vote we go super cheesy and maintain JSON files in GitHub with the active version information. GitHub manages permissions, we can run the changes through CI, we have a process for handling PRs already, anyone can edit them.
The Crash Stats site already has code for figuring out active versions and caching that information for an hour. We can adjust that slightly to pull the data from GitHub.
I think this isn't too much work to set up. It'll be better than what we currently have. It's flexible and supports new products. We can change it if it's not working out.
One bad thing is that it requires one of us to merge the PRs. That means it'll take time for new versions to show up on the site. I think that's the trade-off here until the product-details solution works.
I'm going to make this a P2 and take this to work on. Maybe I can get this changed by the end of next week.
If anyone has thoughts, let me know soon.