Closed
Bug 1427780
Opened 6 years ago
Closed 6 years ago
[compare-locales] Release Version 2.6 - plurals
Categories
(Localization Infrastructure and Tools :: compare-locales, enhancement)
Localization Infrastructure and Tools
compare-locales
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: Pike, Assigned: Pike)
References
()
Details
Since 2.5.1, we landed plural forms, and a check for the properties variant of that. Pretty good opportunity to release a 2.6 with those features. https://hg.mozilla.org/l10n/compare-locales/log?rev=%3A%3A8c04181b6733+-+%3A%3ARELEASE_2_5_1 is the list of commits.
Assignee | ||
Comment 1•6 years ago
|
||
https://hg.mozilla.org/l10n/compare-locales/log?rev=%3A%3ARELEASE_2_6+-+%3A%3ARELEASE_2_5_1 https://github.com/Pike/compare-locales/releases/tag/RELEASE_2_6 Marking FIXED. Open question, should we sync compare-locales in m-c? It's just warnings, so there shouldn't be any impact on builds, but then, the next release might easily impact releases, and that would be a smaller landing.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 2•6 years ago
|
||
https://pypi.python.org/pypi/compare-locales/2.6, too.
Assignee: nobody → l10n
Comment 3•6 years ago
|
||
(In reply to Axel Hecht [:Pike] from comment #1) > It's just warnings, so there shouldn't be any impact on builds, > but then, the next release might > easily impact releases, and that would be a smaller landing. Given there's no practical impact for builds, I think it would make more sense to wait for the next release with Fluent 0.5 to sync m-c
You need to log in
before you can comment on or make changes to this bug.
Description
•