Closed
Bug 905292
Opened 11 years ago
Closed 7 years ago
Required Languages for FxOS v1.2
Categories
(Firefox OS Graveyard :: Gaia, defect, P1)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: mtreese, Assigned: chofmann)
References
Details
(Keywords: feature, Whiteboard: [UCID:l10N, FT:l10N, KOI:P1] feature=story c=translation )
No description provided.
Reporter | ||
Comment 1•11 years ago
|
||
This is the meta bug to track all required languages for FxOS v1.2. Individual bugs will be created for each required language. This bug will be closed when all required translations for FxOS v1.2 are completed.
blocking-b2g: --- → koi+
Keywords: feature
Reporter | ||
Updated•11 years ago
|
Assignee: nobody → chofmann
Assignee | ||
Comment 2•11 years ago
|
||
we probably need some way to track as a "requested locale" --- when bd hears of a partner with interest and then the transition to a "committed locale" when we have a team in place, a partial translation done for evaluation, and we have scoped and evaluated all the other technical issues around delivering a locale such as the things listed here: https://wiki.mozilla.org/L10n:B2G/Adding_Locales
Assignee | ||
Comment 3•11 years ago
|
||
maybe status = new means requested and status = assigned means committed or tracking and on pace to deliver.
Reporter | ||
Comment 4•11 years ago
|
||
+1, let's use 'status = new' for requests on the launguage specific bugs, and 'stuat = assigned' when it is approved and committed
Comment 5•11 years ago
|
||
Should we even file a bug for a 'requested locale'? I think giving the l10n team a heads up makes sense, but why file a bug for something that we *may* want to do? I'm afraid it will cause confusion. I'm okay with what's in comment 4, but would rather keep things clean.
Assignee | ||
Comment 6•11 years ago
|
||
(In reply to Chris Lee [:clee] from comment #5) > Should we even file a bug for a 'requested locale'? > > I think giving the l10n team a heads up makes sense, but why file a bug for > something that we *may* want to do? > I'd like to error on the side of starting the conversations about a locale earlier rather than later, and would actually like to make the final commitment closer to the point when we have most of the work done. that reduces risk dramatically. the only way to to that is to file bugs early. > I'm afraid it will cause confusion. I'm okay with what's in comment 4, but > would rather keep things clean. I don't think having a bunch of "new" localization bugs on file will create much of a problem. We have done similar tracking for 80+ locales on the desktop for similar kinds of tracking issues. We can get our "clean" list with a simple query adjustment that picks up just the "assigned" bugs and removes the "new" bugs from the list.
Comment 12•11 years ago
|
||
Please make this bug track individual languages only. The language list doesn't block anything, nor do particular feature block this bug. They may block particular languages that are tracked by this bug and thus show up deeper in the dependency tree.
Comment 13•11 years ago
|
||
(In reply to Axel Hecht [:Pike] from comment #12) > Please make this bug track individual languages only. The language list > doesn't block anything, nor do particular feature block this bug. They may > block particular languages that are tracked by this bug and thus show up > deeper in the dependency tree. Right. Meta bugs don't block the release themselves - only the actionable dependencies do. This should be removed from the blocking list.
Comment 16•11 years ago
|
||
Not blocking on any meta bugs - nom the dependencies that are actionable.
blocking-b2g: koi+ → ---
Comment 17•7 years ago
|
||
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•