Closed
Bug 1311209
Opened 9 years ago
Closed 8 years ago
Update all-locales for SeaMonkey
Categories
(SeaMonkey :: Build Config, defect)
SeaMonkey
Build Config
Tracking
(seamonkey2.48 fixed, seamonkey2.49esr fixed, seamonkey2.50 fixed, seamonkey2.51 fixed, seamonkey2.52 fixed)
RESOLVED
FIXED
seamonkey2.52
People
(Reporter: iannbugzilla, Assigned: ewong)
References
Details
Attachments
(1 file)
564 bytes,
patch
|
kairo
:
review+
iannbugzilla
:
approval-comm-aurora+
iannbugzilla
:
approval-comm-beta+
iannbugzilla
:
approval-comm-release+
iannbugzilla
:
approval-comm-esr52+
|
Details | Diff | Splinter Review |
At the moment all-locales under suite/locales does not seem to reflect what we ship.
Also see https://bugzilla.mozilla.org/show_bug.cgi?id=1307995
Looking at 2.40 download options, as far as I can see we need to remove:
be
da
ka
ro
si
One that is not on the download page, but seems fairly active is:
pt-BR
so should we be shipping that?
We've also had a request to allow localisation of Kabyle (kab) but that should be a separate bug...
![]() |
||
Comment 1•9 years ago
|
||
I think we should ship pt-BR if we can. Other than that, don't know.
![]() |
Assignee | |
Comment 3•9 years ago
|
||
(In reply to Ian Neal from comment #0)
> At the moment all-locales under suite/locales does not seem to reflect what
> we ship.
> Also see https://bugzilla.mozilla.org/show_bug.cgi?id=1307995
> Looking at 2.40 download options, as far as I can see we need to remove:
> be
> da
> ka
> ro
> si
>
> One that is not on the download page, but seems fairly active is:
> pt-BR
>
> so should we be shipping that?
>
> We've also had a request to allow localisation of Kabyle (kab) but that
> should be a separate bug...
be was only recently removed as a localization and as I understand it,
it still works in be.
However, when doing repacks, we don't look at all-locales; but,
shipped-locales. I don't know what all-locales is used for.
KaiRo?
Flags: needinfo?(ewong) → needinfo?(kairo)
![]() |
||
Comment 4•9 years ago
|
||
(In reply to Edmund Wong (:ewong) from comment #3)
> KaiRo?
IIRC all-locales was what Nightly and those branches were building out of automation, shipped-locales is what the beta/release build process looks at.
Flags: needinfo?(kairo)
![]() |
Assignee | |
Comment 5•9 years ago
|
||
(In reply to Robert Kaiser from comment #4)
> (In reply to Edmund Wong (:ewong) from comment #3)
> > KaiRo?
>
> IIRC all-locales was what Nightly and those branches were building out of
> automation, shipped-locales is what the beta/release build process looks at.
Thanks KaiRo for the clarification.
![]() |
||
Comment 6•9 years ago
|
||
And, FWIW, that means that all-locales are all that we support / have teams working on at any level, while shipped-locales means those we actually ship, and the latter should always be a subset of the former.
Comment 7•9 years ago
|
||
To sum up: we have to update the shipped-locales file, not the all-locales one.
Flags: needinfo?(akalla)
![]() |
Assignee | |
Comment 8•9 years ago
|
||
Aiui, only be needs to be removed (need to point be-users to ru).
![]() |
||
Comment 9•8 years ago
|
||
Comment on attachment 8828184 [details] [diff] [review]
proposed patch
Review of attachment 8828184 [details] [diff] [review]:
-----------------------------------------------------------------
::: suite/locales/all-locales
@@ -1,1 @@
> -be
Hmm, do we know that the be team is not interested in working on SeaMonkey any more? We only should remove from all-locales if it's officially abandoned (this file is only used for l10n-repacks on nightly and aurora). For shipped-locales, it's fine to remove if the respective release doesn't build and we aren't gonna ship in that language.
Make sure we update the affected release announcement message when we add/remove entries in shipped-locales.
![]() |
Assignee | |
Comment 11•8 years ago
|
||
(In reply to Robert Kaiser from comment #10)
> Edmund, see comment #9 for my question ;-)
Point taken. Haven't pinged anyone from the be localization team. Who is on point for the be localization team?
Flags: needinfo?(ewong)
![]() |
||
Comment 12•8 years ago
|
||
(In reply to Edmund Wong (:ewong) from comment #11)
> (In reply to Robert Kaiser from comment #10)
> > Edmund, see comment #9 for my question ;-)
>
> Point taken. Haven't pinged anyone from the be localization team. Who is
> on point for the be localization team?
https://wiki.mozilla.org/L10n:Teams:be is the contacts page for that team.
![]() |
||
Comment 13•8 years ago
|
||
Comment on attachment 8828184 [details] [diff] [review]
proposed patch
Review of attachment 8828184 [details] [diff] [review]:
-----------------------------------------------------------------
r+ based on email exchange with the team, thanks ewong!
Attachment #8828184 -
Flags: review?(kairo) → review+
![]() |
Assignee | |
Comment 14•8 years ago
|
||
OTR, I contacted the be contact and was told that none of the
be localizers are interested in doing localizations for SeaMonkey.
![]() |
Assignee | |
Comment 15•8 years ago
|
||
Pushed to comm-central:
https://hg.mozilla.org/comm-central/rev/495489dbbfa52f82c5b82abddd2256219aabbc2c
![]() |
Assignee | |
Comment 16•8 years ago
|
||
Comment on attachment 8828184 [details] [diff] [review]
proposed patch
[Approval Request Comment]
Regression caused by (bug #): 1307995
User impact if declined:
Testing completed (on m-c, etc.):
Risk to taking this patch (and alternatives if risky): None
String changes made by this patch: None
Be was removed from releases in Moco since Gecko 51, so we need this
patch pushed to c-a to c-r (future 2.48 relbranch and 2.49 release)
Attachment #8828184 -
Flags: approval-comm-release?
Attachment #8828184 -
Flags: approval-comm-beta?
Attachment #8828184 -
Flags: approval-comm-aurora?
Reporter | ||
Comment 17•8 years ago
|
||
Comment on attachment 8828184 [details] [diff] [review]
proposed patch
a=me where needed
Attachment #8828184 -
Flags: approval-comm-release?
Attachment #8828184 -
Flags: approval-comm-release+
Attachment #8828184 -
Flags: approval-comm-beta?
Attachment #8828184 -
Flags: approval-comm-beta+
Attachment #8828184 -
Flags: approval-comm-aurora?
Attachment #8828184 -
Flags: approval-comm-aurora+
![]() |
Assignee | |
Comment 18•8 years ago
|
||
Pushed to comm-beta:
https://hg.mozilla.org/releases/comm-beta/rev/c863825b864e (default)
https://hg.mozilla.org/releases/comm-beta/rev/630c22cbc776 (relbranch)
![]() |
Assignee | |
Updated•8 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
![]() |
||
Comment 19•8 years ago
|
||
Comment on attachment 8828184 [details] [diff] [review]
proposed patch
This one never made it to esr52
Attachment #8828184 -
Flags: approval-comm-esr52?
![]() |
||
Updated•8 years ago
|
status-seamonkey2.49esr:
--- → affected
Reporter | ||
Comment 20•8 years ago
|
||
Comment on attachment 8828184 [details] [diff] [review]
proposed patch
a=me
Attachment #8828184 -
Flags: approval-comm-esr52? → approval-comm-esr52+
![]() |
||
Comment 21•8 years ago
|
||
status-seamonkey2.50:
--- → fixed
status-seamonkey2.51:
--- → fixed
status-seamonkey2.52:
--- → fixed
Target Milestone: --- → seamonkey2.52
![]() |
||
Updated•8 years ago
|
status-seamonkey2.48:
--- → fixed
You need to log in
before you can comment on or make changes to this bug.
Description
•