[pl][v1.1] Sign-off for Polish l10n of Firefox for iOS v1.1

RESOLVED FIXED

Status

Mozilla Localizations
pl / Polish
RESOLVED FIXED
2 years ago
2 years ago

People

(Reporter: Pike, Assigned: stef)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

2 years ago
This bug is for signing off on your localization for shipping it in Firefox for iOS v1.1. Please close this bug as RESOLVED FIXED by 12 October if you are comfortable with your localization work shipping in Firefox for iOS v1.1.
(Reporter)

Updated

2 years ago
Blocks: 1212475
(Assignee)

Updated

2 years ago
Assignee: nobody → splewako
Hi Stefan,

Is Polish ready to ship in v1.1?

Jeff
(Assignee)

Comment 2

2 years ago
(In reply to Jeff Beatty [:gueroJeff] from comment #1)
> Is Polish ready to ship in v1.1?

Polish localization is in best possible shape but I not sure the project is ready to ship Polish localization.
(In reply to Stefan Plewako [:stef] from comment #2)
> (In reply to Jeff Beatty [:gueroJeff] from comment #1)
> > Is Polish ready to ship in v1.1?
> 
> Polish localization is in best possible shape but I not sure the project is
> ready to ship Polish localization.

I'm not sure I understand what you're implying. Shall I assume that you don't intend to ship Polish in v1.1?
(Assignee)

Comment 4

2 years ago
I'm implying that project localizability seems noticeably worse then it was around 1.0 and reported issues aren't worked on to the point where I'm not sure if we should ship (otherwise ready) pl localization with 1.1, especially when considering the fact that Mozilla didn't really shipped 1.0 to Polish users (signed-off in bug 1140708).

Depended bugs status doesn't necessarily mean much in this bug context but it is still better to have them also listed here than to allow them to get lost in bug 1092387 depended list.
I agree that these are challenges to localizability in the product, affecting all locales. The scope of this bug, however, is to determine whether the work you have submitted is completed (within your control) and is of the best quality to be exposed to users in a shipped release. If you feel that this is the case, please sign off. We can raise flags about these localizability bugs to the iOS team and get some understanding of when they can address and resolve them, in the mean time.
(Assignee)

Comment 6

2 years ago
(In reply to Jeff Beatty [:gueroJeff] from comment #5)
> The scope of this bug, however, is to determine
> whether the work you have submitted is completed (within your control) and
> is of the best quality to be exposed to users in a shipped release.

The thing is, I don't believe it is possible nor helpful to make that kind of assertions ignoring project localizability shape and state. Whole l10n sign-off concept doesn't really work well with products without stable localizability.
Your objections are noted. 

The deadline is here. We're not going to ship Polish in v1.1 without an explicit sign off. If you're not willing to do that by 5:00PM, Pacific Daylight Time, we'll have to proceed to build and ship without Polish.
(Assignee)

Comment 8

2 years ago
One more question, is this specific revision sign-off or future revisions up until some point will be also taken into release?
We don't have code that performs in that way and it would add risk to the overall shipping status to add it. For this release, we're only taking the head revision.
(Assignee)

Comment 10

2 years ago
Head revision in the time of signing or in the time of building?
(Reporter)

Comment 11

2 years ago
Head revision at some point in time in between those two. There's no commitment to take or not take particular commits in svn between now and the time we build the RCs and/or final builds.
(Assignee)

Comment 12

2 years ago
OK, thank you. Please include Polish in 1.1.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → FIXED
Thanks Stef :-)
(Assignee)

Updated

2 years ago
Depends on: 1215286
(Assignee)

Updated

2 years ago
Depends on: 1216142
(Assignee)

Updated

2 years ago
Depends on: 1153333
You need to log in before you can comment on or make changes to this bug.