Connect firefox version to V3 API fixes #3042

[jaredlockhart]

This hooks the firefox version up to the API/DB. Then we can serialize it out separately in #2965

[pdehaan]

Q1: How will this work when, say, Firefox 83 is current Release channel? Would we still have older ex-Release versions listed at the top of the <select> menu?
Q2: Do we have to modify this menu after every new release is released?
Q3: Does the <select> menu preselect the current Release channel version?

[jaredlockhart]

Q1: How will this work when, say, Firefox 83 is current Release channel? Would we still have older ex-Release versions listed at the top of the <select> menu?

The list is static right now so the options presented won't change unless we explicitly change them. Is that what you mean?

Q2: Do we have to modify this menu after every new release is released?

Well right now it goes up to 100, so I guess when we get close to that we'll dump a bunch more options in. Why would we need to do it after every release?

Q3: Does the <select> menu preselect the current Release channel version?

To do that we'd have to have knowledge of the release calendar, which would require a bunch of work to pull it in from somewhere and update the UI with it, etc. @AnaMedinac asked for the same thing, but we haven't done anything like that yet.

[pdehaan]

Currently looks like:

I think my concerns are if Firefox 83 is release, we'd have ~6 old builds at the top of the list that don't make sense. Or each new experiment would always have to select the correct Release version from a dropdown. Or if you mistakenly select "Firefox 94.0" from the dropdown (because reasons), the experiment would launch (if not caught+rejected by an operator), but nothing would happen because even after your enrollment+test period, that version would never be in scope and you'd presumably get no results back.

But yeah, maybe its too tricky to scrape the list of current trains from https://whattrainisitnow.com/ (or the upstream https://product-details.mozilla.org/1.0/firefox_versions.json which is where they apparently fetch from). Having a pseudo-dynamic list of dropdown values adds a lot of weird edges.
I just didn't know if a select list with only 3 options ("Release Firefox 78.0", "Beta Firefox 79.0", and "Nightly Firefox 80.0") would make it easier an easier UX for experiment submitters. Since we only ever show 3 options, "Release" would always be the first/default option and what submitters would want 99.99% of the time anyways.

[jaredlockhart]

@pdehaan Yeah these are all very valid and good points, I'd suggest taking it out of here and moving exactly what you just wrote into #2948, which I just reopened, so that we can think through it in more detail. Also thank you for the detailed write up!

[tiftran]

looks good to me