Closed Bug 379054 (fx2006l10n) Opened 18 years ago Closed 17 years ago

Ship pending locales for Firefox 2.0.0.6

Categories

(Firefox :: General, defect)

2.0 Branch
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: Pike, Assigned: Pike)

References

Details

We're having more locales pending shipping for 2.0.0.5.
Flags: blocking1.8.1.5+
Depends on: fx20-hy-AM, fx20-sq, fx20-uk
blocking bugs should be assigned to a real address. Need a patch of some kind, code-freeze is July 13
Assignee: nobody → l10n
2.0.0.5 just turned into a firedrill. Not shipping any new languages this time.
Flags: blocking1.8.1.5+ → blocking1.8.1.6+
Alias: fx2005 → fx2006
Summary: Ship pending locales for Firefox 2.0.0.5 → Ship pending locales for Firefox 2.0.0.6
Kurdish (ku) looks ready to me. All bugs mentioned in the trackingbug 369478 have been fixed and verified in Firefox 2.0.0.5 . Could someone else please confirm this so we can finally go out of beta?
Changing the alias; the conflicts with the aliasing I'd like to start using for releases (plus, this is l10n-focused, not 2.0.0.6 focused)
Alias: fx2006 → fx2006l10n
Axel closed bug #369478, what does it mean for the pending ku locale? In Firefox 2.0.0.6 it is still in beta. Does it become official now?
No longer depends on: fx20-hy-AM
Axel: is this bug about shipping a 2.0.0.6 (prior) version of Kurdish, or about updating the shipped-locales file for the "next" version (currently 2.0.0.8)? That is, is this a blocking bug or a side effort?
It is now about shipping a prior version, but when it was filed 2.0.0.6 was still a coming version. This gets deferred somehow always since 2.0.0.4. We are not aware of any open issues and don't know why it is not being shipped.
I don't know why it isn't being shipped either (maybe it is? the "ship ku" bug is marked closed), but yesterday was the scheduled FF2.0.0.8 code freeze so whatever needed to happen should have happened by then. Taking this bug off the blocking list.
Flags: blocking1.8.1.8+
Resolving incomplete, we did all we could for .6. I started off with filing bugs per release, but that doesn't cut it, like, it doesn't cover beta or not and other meta data. I'll work on a replacement offline.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.