Closed Bug 359705 Opened 18 years ago Closed 17 years ago

Branch Georgian [ka] for Firefox 2.0.0.1

Categories

(Mozilla Localizations :: Other, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: giasher, Unassigned)

References

Details

(Keywords: fixed1.8)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; ka-GE; rv:1.9a1) Gecko/20061101 SeaMonkey/1.5a
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; ka-GE; rv:1.9a1) Gecko/20061101 SeaMonkey/1.5a

We would like to request approval to branch the Georgian locale to the stable 1.8 branch
It's quet matured. Files in trunk already uploaded - http://lxr.mozilla.org/l10n/source/ka/

Reproducible: Always
a=l10n@mozilla.com for branching ka onto the 1.8 branch.

We need to get Georgian built, still, but I'll try to pack that up with at least kurdish, too, in a separate bug.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Gia, could you do this rather sooner than later? We should have enough time to do as many tests as possible on the actual mozilla-generated builds.
not sure i made right steps after Your message ... branching the trunk to 1_8 [myself]
http://lxr.mozilla.org/l10n-mozilla1.8/source/ka/
Depends on: 360743
Gia, I'm seeing a bunch of changes on the branch after the merge.

The MOZILLA_1_8_BRANCH is frozen, that means, if you want to land changes, you should file a bug on the problems, create a patch, attach that patch to the bug and request approval1.8.1.1 (that's the flag for this period).

Please don't land things without approval.

In addition, you should land patches on branches, not rebranch for each change.
Status: NEW → ASSIGNED
this issue fixed for 1.8.1.1 and now for 1.8.1.5
can i mark it as fixed1.8.1.1 and then verified1.8.1.1?
Keywords: fixed1.8
The way this is fixed is good enough. We need the release specific flags for fixed and verified really only when there are patches with branch specific approvals.

Closing this one out.
Status: ASSIGNED → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.