Closed Bug 657272 Opened 14 years ago Closed 14 years ago

Investigate need for aus updates from 2.1b2 -> 2.1final for locales dropped from b3

Categories

(SeaMonkey :: Release Engineering, defect)

x86
Windows 7
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: Callek, Assigned: kairo)

References

Details

Attachments

(1 file)

We should gather data on how many ADU we have on the various locales we had to drop for b3, since the update automation did not generate locales for our b2->final for those locales. Generating updates will be time consuming and manual work for those various locales. Having actual data will help prioritize that work. KaiRo said he has access to the ADU numbers in a more direct way now, so this shouldn't be too difficult to gather. For reference we care about 2.0.x users (total), 2.1 users (all versions separate and total) for the following locales: `it`, `fi`, `nb-NO`, `sv-SE`
=Average Blocklist ping ADU from last week= * Screenshot: http://screencast.com/t/yianZxrk * Query: select NON EMPTY Crossjoin({[Locale Codes].[fi], [Locale Codes].[it], [Locale Codes].[nb-NO], [Locale Codes].[sv-SE]}, {[Measures].[Average Requests per Day]}) ON COLUMNS, NON EMPTY {[Products].[SeaMonkey], [Products].[SeaMonkey].[Other].[2.1], [Products].[SeaMonkey].[Other].[2.1b2], [Products].[SeaMonkey].[Other].[2.1b3], [Products].[SeaMonkey].[Other].[2.0.13], [Products].[SeaMonkey].[Other].[2.0.14]} ON ROWS from [BlockList Analysis] where {[Date].[2011].[5].[9], [Date].[2011].[5].[10], [Date].[2011].[5].[11], [Date].[2011].[5].[12], [Date].[2011].[5].[13], [Date].[2011].[5].[14], [Date].[2011].[5].[15]} * Results: fi it nb-NO sv-SE All SeaMonkey 588 14,301 538 1,578 2.1 1 10 2 8 2.1b2 12 42 8 15 2.0.13 54 904 53 140 2.0.14 499 11,198 418 1,258
Please close this bug out if this data answers your question. Otherwise, just let me know what I missed.
(In reply to comment #0) > For reference we care about 2.0.x users (total), 2.1 users (all versions > separate and total) for the following locales: `it`, `fi`, `nb-NO`, `sv-SE` (In reply to comment #2) > Please close this bug out if this data answers your question. Otherwise, > just let me know what I missed. Missing data is those locales, for 2.1b1, 2.1a3, 2.1a2, and 2.1a1 I bet the latter stuff will be negligible, but want to be sure.
The alphas don't have L10n, so you'll have zero for them.
I found where I can get the data myself now. :) The attached XLS is from this query: select NON EMPTY Crossjoin({[Locale Codes].Children}, {[Measures].[Average Requests per Day]}) ON COLUMNS, NON EMPTY {[Products].[SeaMonkey], [Products].[SeaMonkey].[Other].[2.0.13], [Products].[SeaMonkey].[Other].[2.0.14], [Products].[SeaMonkey].[Other].[2.1a1], [Products].[SeaMonkey].[Other].[2.1a2], [Products].[SeaMonkey].[Other].[2.1a3], [Products].[SeaMonkey].[Other].[2.1b1], [Products].[SeaMonkey].[Other].[2.1b2], [Products].[SeaMonkey].[Other].[2.1b3], [Products].[SeaMonkey].[Other].[2.1]} ON ROWS from [BlockList Analysis] where {[Date].[2011].[5].[19], [Date].[2011].[5].[20], [Date].[2011].[5].[21], [Date].[2011].[5].[22], [Date].[2011].[5].[23], [Date].[2011].[5].[24], [Date].[2011].[5].[25]} Numbers for the locales in question (plus comparisons, empty means 0): total en-US fi it nb-NO sv-SE 2.0.13 37868 20667 44 549 24 92 2.0.14 575873 265892 502 11600 528 1332 2.1a1 72 72 2.1a2 64 64 2.1a3 65 65 2.1b1 868 760 2.1b2 814 572 15 49 6 2.1b3 3181 2557 2.1 10927 6831 10 461 4 38 Numbers for locales we have shipped in 2.0.14 but not in 2.1 (yet): be ca gl hu ka tr zh-CN 2.0.13 1 78 233 2 16 58 2.0.14 34 1693 29 7871 42 241 763 (no numbers for any 2.1* builds, of course)
As a related note and reference, those are the percentages of all locales we ever shipped in 2.0 from the total data of SeaMonkey blocklist pings in this week: be 0,01% ca 0,25% cs 1,69% de 22,27% en-GB 2,25% en-US 47,44% es-AR 0,60% es-ES 1,12% fi 0,08% fr 3,02% gl 0,01% hu 1,25% it 1,99% ja 1,12% ja-JP-mac 0,16% ka 0,01% lt 0,27% nb-NO 0,08% nl 0,75% pl 5,29% pt-PT 0,35% ru 9,28% sk 0,22% sv-SE 0,21% tr 0,04% zh-CN 0,12%
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: