The default bug view has changed. See this FAQ.
Bug 456266 (fx35-l10n-tracker)

[tracking] Firefox 3.5 l10n release trackers

RESOLVED FIXED

Status

Core Graveyard
Tracking
RESOLVED FIXED
9 years ago
8 months ago

People

(Reporter: Pike, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

9 years ago
This is a meta bug used to track the status of Firefox 3.1 l10n release trackers.
(Reporter)

Updated

9 years ago
Depends on: 463437
(Reporter)

Updated

9 years ago
Depends on: 463600

Updated

8 years ago
Depends on: 467560
(Reporter)

Updated

8 years ago
No longer depends on: 467560
(Reporter)

Updated

8 years ago
Depends on: 443139
(Reporter)

Updated

8 years ago
Depends on: 415641
(Reporter)

Updated

8 years ago
Depends on: 415672
Depends on: 415622
Depends on: 477988
(Reporter)

Comment 1

8 years ago
Morphing this bug over 3.5.
Alias: fx31-l10n-tracker → fx35-l10n-tracker
Summary: [tracking] Firefox 3.1 l10n release trackers → [tracking] Firefox 3.5 l10n release trackers
(Reporter)

Updated

8 years ago
Depends on: 482497
(Reporter)

Updated

8 years ago
Depends on: 482507
Depends on: 482511

Updated

8 years ago
Depends on: 482514
Depends on: 415587
(Reporter)

Updated

8 years ago
Depends on: 483285
Any plans on a tracker for Persian (fa)?
Ehsan: the release tracker bugs are filed for the first release of a locale. This means that all the locales blocking this bug will be released for the first time in 3.5. Consequently, there will be no 3.0.x versions.

For Persian, we still have bug 415597, the Firefox 3 l10n tracker, meaning that Persian is on track for a release on the 3.0.x branch. This doesn't mean there won't be any 3.5 release of Persian, of course. It just means that the first release is targeted on the 3.0.x branch. 

Hence, we don't really need a 3.5 tracker for Persian. That is, unless you'd like to drop 3.0.x and release only on 3.5. In that case we'd morph the fx3 tracker into a fx35 one.

I hope this is clear. Please let me know if you have any comments or questions.
Thanks for the explanation, Staś.  Actually we would like to drop the Firefox 3.0.x release, and proceed with 3.5, and so far all of our efforts have been targeted at 3.5 (we released with 3.1 Beta 3 for the first time).  So, I will morph bug 415597 into a fx35 release tracker.  I hope that's OK.  :-)

Updated

8 years ago
Depends on: 415597
Depends on: 415682
(Reporter)

Updated

8 years ago
Depends on: 492592
(Reporter)

Updated

8 years ago
Depends on: 492595
(Reporter)

Updated

8 years ago
Depends on: 492967
(Reporter)

Updated

7 years ago
No longer depends on: 483285
(Reporter)

Updated

7 years ago
No longer depends on: 482507
(Reporter)

Updated

6 years ago
No longer depends on: 415682
(Reporter)

Updated

6 years ago
No longer depends on: 492592
(Reporter)

Updated

6 years ago
No longer depends on: 415622
(Reporter)

Updated

6 years ago
No longer depends on: 492967
(Reporter)

Updated

6 years ago
No longer depends on: 415641
(Reporter)

Updated

6 years ago
No longer depends on: 415587
(Reporter)

Updated

6 years ago
No longer depends on: 482514
(Reporter)

Comment 5

6 years ago
We're done with Firefox 3.5, I moved the remaining locales over to block the now version-independent tracker (that used to be 4.0).
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
(Assignee)

Updated

8 months ago
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.