This is a tracker bug for releasing Firefox 3 fa. This bug is not that detailed, but as we get particular work items, they should block this bug for tracking, and better discoverability. This is currently blocked by branching for Firefox 2, or at least deciding on that, so adding that dependency.

Should this bug be closed as a dupe of bug 412273 (or the other way around)?

I don't care about bug 412273, I will continue to use this bug to make a call on when we're ready to ship Firefox 3 in Persian. Make sure to make this bug only be blocked by things which should keep us from shipping a persian release of Firefox 3.

(In reply to comment #2) > I don't care about bug 412273, I will continue to use this bug to make a call > on when we're ready to ship Firefox 3 in Persian. I marked bug 412273 as a dupe of this bug. > Make sure to make this bug only be blocked by things which should keep us from > shipping a persian release of Firefox 3. I've been adding all of the candidates for such bugs as deps of this bug. I'll need to triage them to make sure this bug only depends on the crucial stuff for Persian Firefox 3 release.

(In reply to bug 435856, comment #1) > Does this bug really block releasing a Persian version of Firefox? As that is > what blocking bug 415597 indicates. No, it doesn't block the Persian release actually. I used to keep track of Firefox 3.0 problems with Persian language on Persian-Fx3.0, which has been closed as a DUP of this bug. I think we need to get that back, and clean up dependencies of this bug. For example, bug 337274 is not actually a blocker here too. Ehsan, should we reopen Persian-Fx3.0?

(In reply to comment #5) > (In reply to bug 435856, comment #1) > > Does this bug really block releasing a Persian version of Firefox? As that is > > what blocking bug 415597 indicates. > > No, it doesn't block the Persian release actually. > > I used to keep track of Firefox 3.0 problems with Persian language on > Persian-Fx3.0, which has been closed as a DUP of this bug. I think we need to > get that back, and clean up dependencies of this bug. For example, bug 337274 > is not actually a blocker here too. > > Ehsan, should we reopen Persian-Fx3.0? Please see comment 2. That was the reason I closed bug Persian-Fx3.0. I think we should either re-open that bug or file a new bug to track the issues related to Persian Firefox 3.0, and initially move *all* of the dependencies of this bug to that one, and then we can start working over them and make the ones we think are worth enough to block the release of Persian Fx3.0 block this bug. Then, we can track both what is essential for the first release of Persian Fx3.0, and what would be nice to have but is not that crucial. What do you think, Behnam?

Ok, seems the problem comes from the title of the other bug, "Persian Firefox 3.0 tracker" which should be "Tracker of Persian support bugs in Firefox 3.0". Everyone is OK with opening the other bug, and clean up here?

Yeah, please go ahead and do that. I don't think Axel objects to this, according to comment 2.

Removing unnecessary dependencies. All has been added as a dep for bug 412273.

Morphing this to track the 3.5 release for Persian (fa).

Removing the fixed stuff or those which are not blockers for the 3.5 release from the dependency list. I will add anything removed from here as a dependency for bug 285718 (for tracking purposes) if it's already not.

All blocker bugs for Persian (fa) release are fixed as of now. Keeping this bug open to track any possible future bugs.

Nah, nothing blocking no more here, resolving FIXED.