530808 - [shipping] support locales in beta

Status: RESOLVED INCOMPLETE

(Webtools Graveyard :: Elmo, defect, P2)

Description

[Axel Hecht [:Pike]]

We should store our beta status inside the dashboard, too. Should probably be in the shipping app.

I wonder if we should do something event based again.

I'd hook them up to App. Looking at our current work on de-beta, it doesn't seem to make sense to track, say Malayalam, independently on 3.5 and on 3.6. If they're going out of beta in one, they de-beta in the other.

Sounds good?

Comment 1

[Zibi Braniecki [:zbraniecki][:gandalf]]

Would it make sense to have a Status model with hooks to Locale and App and status value "beta", "not yet", "production"?

Events could be used to store information on status changes.

Comment 2

[Axel Hecht [:Pike]]

According to our triage call, we need to hook this up to AppVersion instead of App, web site and services etc can be in beta stage.

Comment 3

[Staś Małolepszy :stas]

Also as per our call, some locales can actually move back into beta for verious reasons (e.g. tr final in 3.0, beta in 3.5, iirc).

Comment 4

[Axel Hecht [:Pike]]

With the new release train, this is gonna change slightly. Not exactly sure how, but it'll depend on bug 650816, data1.1.

Comment 5

[Laura Thomson :laura]

Where would this data come from?

Comment 6

[Axel Hecht [:Pike]]

We'd want to keep this inside elmo, and then convert out to releng (via l10n-changesets etc) and possibly to product-details at some time further down.

Comment 7

[Axel Hecht [:Pike]]

Clearing this out. We track beta status now in the PM project, and try to keep data in elmo lightweight, so the original idea doesn't apply anymore today.