734833 - Featured versions list should update themselves automatically

Status: RESOLVED WONTFIX

(Socorro :: Webapp, task)

Description

[Mark Banner (:standard8)]

Socorro should be able to update its featured versions automatically - the version listing is well know, and presumably Socorro has information about branches.

Therefore we should be able to work out a method for update the feature versions automatically. This would save additional (slow) checkbox work every week or so.

Given the current states, I would suggest that it is configured to show by default:

- Latest release
- Latest Beta
- Latest 'special' branch (i.e. ESR)

Comment 1

[Robert Kaiser]

I have always been and still am strictly against that. We prepare builds often days before they are shipped, and they get added to Socorro when they appear on FTP as candidates. At that stage, we don't want to have them "featured" yet, but only once we actually get reasonable data in, which usually is the day after we shipped at the earliest. Also, we never want ESR to be "featured" ever, at least for Firefox, we ought to not watch crash stats for them anyhow (no direct support for those people), we only want to be able to look into them as needed, but never focus on them on the front page.

Comment 2

[Mark Banner (:standard8)]

(In reply to Robert Kaiser (:[e-mail]) from comment #1)
> I have always been and still am strictly against that. We prepare builds
> often days before they are shipped, and they get added to Socorro when they
> appear on FTP as candidates. At that stage, we don't want to have them
> "featured" yet, but only once we actually get reasonable data in, which
> usually is the day after we shipped at the earliest.

Then we have sources on the websites that Socorro should be checking, or something else, a threshold of users maybe? or an API?

Any improved interface would be minimal help (updating individual versions for featured is really bad, it should just be a pick list), but I don't see people logging in each week just to update that for betas etc.


> Also, we never want ESR
> to be "featured" ever, at least for Firefox, we ought to not watch crash
> stats for them anyhow (no direct support for those people), we only want to
> be able to look into them as needed, but never focus on them on the front
> page.

Ok, that's a separate issue.

Comment 3

[Robert Kaiser]

(In reply to Mark Banner (:standard8) from comment #2)
> Then we have sources on the websites that Socorro should be checking, or
> something else, a threshold of users maybe? or an API?

An API wouldn't simplify this. I have thought about a threshold but it also isn't easy, e.g. we want a Firefox beta to be listed once it's out with a number of users, but the previous one can still have way more users - and in source uplift time, we had times where the new beta wasn't there yet and it was better to list both the new and the last release instead.

It's not algorithmic, it's mostly a preference of those working closely with the site.

> Any improved interface would be minimal help (updating individual versions
> for featured is really bad, it should just be a pick list), but I don't see
> people logging in each week just to update that for betas etc.

I see no problem with logging in daily and updating it, I'm doing that routinely quite often. But I agree that it should be simpler, editing two versions and having two page reloads just for switching a single featured version is annoying.