ICU Meeting Minutes 2013-2014 (Archived)

Current and past meeting minutes

2014/12/24 & 2014/12/31 - No meetings

2014/12/17

  1. ICU 55 Milestone 1
  1. BRS
  2. Reviews
  3. Download page
  1. ICU 55m1 tickets “fixed” or “fixedbyotherticket
  1. [capitalization WG?] (Mark)
  1. separate meeting - sometime after Jan 7? - Jan 9 / cldr overflow time slot?
  2. Mark will send the invitation - to Peter, Markus; anyone else?
  1. API Proposals for ICU 55
  2. IncomingBugs
  1. Anybody - fix compiler warnings per #11428
  2. http://source.icu-project.org/repos/icu/icu/tags/release-52-1/source/data/misc/supplementalData.txt (search for territoryInfo)

2014/12/10

  1. Capitalization (mark)
  1. for menu- Mark, Markus, Peter to look at this
  2. Use special code for capitalizing, not a break iterator
  3. Need to use the right contextTrasform data depending on (1) display locale, (2) what is being capitalized (language name, keyword, key value, month name, etc.) and (3) context (mid sentence, beginning of sentence, menu, standalone, etc.).
  1. ICU 55 Milestone 1
  1. BRS
  2. Review
  3. CLDR data integration (#11417)
  4. Download page - please update download page
  1. IncomingBugs * Reviews

2014/12/03

  1. SpoofChecker [Mark]
  1. ICU 54 did not include 7.0 data update for spoof check
  2. Immediate request: don’t adopt 7.0 confusable data (we can take the mod data)
  3. Request of the UTC to removed filtered tables, and revert mappings where possible to match 6.3
  4. Mark to propose.
  1. Important bug fixes affecting already released versions
  1. “maintenance” tickets - after 54 GA
  1. #11326 ICUResourceBundleReader.getString fails on Java 6 (J 54 GA only, fixed by 54.0.1)
  2. #11363 SimpleDateFormat clone problem (J, under review)
  3. #11388 ICU4J 53/54 Latin collation bug, not transitive (already merged to maint 53/54)
  1. “sensitive” tickets - after 54 GA
  1. #11369 Heap-buffer-overflow in RegexMatcher::MatchChunkAt
  2. #11370 missing range check in regex
  3. #11371 Integer overflow issue in URX_BUILD
  4. #11389 Fix low memory crashers in dtpgen, timezone
  1. Policy for merging fixes to back level releases?
  1. Sensitive flag review - BRS / uncheck sensitive already fixed in version (currenct - 2)
  1. 54.x maintenance release?
  1. Collation bug (#11388 J only, Collator built from rules “only”, compare() not transitive) -> download page (53 & 54) / as known issue of ICU4J
  2. CLDR ticket #8056 “units conversion to ICU is messed up” - need ICU ticket for tracking integration?
  1. Known Issues
  1. ICU tickets with keyword “KnownIssue”
  2. Known Issues - CLDR
  1. #1911
  2. #4375
  3. #6745
  4. #7872
  5. Should we create ICU “counter” ticket for tracking purpose? - No
  6. Concensus: Milestone BRS - check the list of CLDR known issue tickets - update status
  1. Markus: If we want to eliminate “known issues”, then maybe that means that we should not have logKnownIssue() (or “time bombs”) at all? Just disable a failing test and have a ticket for fixing it, without printing warnings, without over-promising to fix it soon?
  2. Add visibility flag in logKnownIssue function (Steven)
  1. data download available like this or this
  1. API Proposals
  1. Regex error code (andy)
    https://docs.google.com/document/d/17bdxIX4J84VV8cv3OGqnY-bAXVSnDDT8yVB03uUo-10/edit#heading=h.2nf20he6bn3k
  1. IncomingBugs * Reviews

2014/11/26 No meeting (Thanksgiving)

(steven may do some trac updates..)

2014/11/19

  1. M1 schedule - see above
  2. Next week - No meeting
  3. API Proposals for ICU 55
  4. IncomingBugs
  5. Timezones and continuous build (Travis)
  6. Reviewing known issues - alert people not on call, add comment about status
  7. Pending Reviews - please address soon

KNOWN ISSUES

#10774 <http://bugs.icu-project.org/trac/ticket/10774> - srl

  /CollationAPITest/TestGetAll/TestGetAll

         "Side effects from utility/LocaleTest/TestGetLocale"

#11020 <http://bugs.icu-project.org/trac/ticket/11020> - tkeep

  /NumberFormatSpecificationTest/TestScientificNotation/TestScientificNotation

#11025 <http://bugs.icu-project.org/trac/ticket/11025> - tkeep

  /NumberFormatSpecificationTest/TestPadding/TestPadding

#11052 <http://bugs.icu-project.org/trac/ticket/11052> - yoshito

  /TimeZoneFormatTest/TestTimeRoundTrip/TestTimeRoundTrip

         "Ambiguous zone name - Samoa Time"

#7270 <http://bugs.icu-project.org/trac/ticket/7270> - andy

  /RBBITest/TestUnicodeFiles/TestUnicodeFiles

#9503 <http://bugs.icu-project.org/trac/ticket/9503> - grhoten

  /TestEnglishSpellout/TestEnglishSpellout

#cldrbug:1911 <http://unicode.org/cldr/trac/ticket/1911> - mark [6 years old]

  /TransliteratorRoundTripTest/TestDevanagariLatin/TestDevanagariLatin

  /TransliteratorRoundTripTest/TestGreek/TestGreek

  /TransliteratorRoundTripTest/TestGreekUNGEGN/TestGreekUNGEGN

  /TransliteratorRoundTripTest/TestHebrew/TestHebrew

  /TransliteratorRoundTripTest/TestInterIndic/TestInterIndic

  /TransliteratorRoundTripTest/Testel/Testel

#cldrbug:6745 <http://unicode.org/cldr/trac/ticket/6745> - (CLDR) markus - low priority and non-trivial and want to keep the test

  /UCAConformanceTest/TestRulesNonIgnorable/TestRulesNonIgnorable

         "UCARules.txt has problems"

KNOWN ISSUES

#11216 <http://bugs.icu-project.org/trac/ticket/11216> - yoshito / Fixed, peter to review

  /tsutil/cldrtest/TestLocaleStructure

         "Duplicate LCID mapping for language hsb"

#11217 <http://bugs.icu-project.org/trac/ticket/11217> - markus

  /tsutil/cldrtest/TestExemplarSet

         "Fix result of uscript_getCode for yi: USCRIPT_YI -> USCRIPT_HEBREW"

  /tsutil/cldrtest/VerifyTranslation

         "Fix result of uscript_getCode for yi: USCRIPT_YI -> USCRIPT_HEBREW"

Known Issues:

[http://bugs.icu-project.org/trac/ticket/10268] - tkeep - marked fixed!

  - ICU/Core/Serializable/CoverageTest (Serializable interface is not implemented in PluralRules$FixedDecimal)

[http://bugs.icu-project.org/trac/ticket/10783] - mark

  - ICU/Core/Format/PluralFormat/PluralRulesTest/TestLimitedAndSamplesConsistency (Fix issues with isLimited vs computeLimited on ordinals)

[http://bugs.icu-project.org/trac/ticket/11020] -tkeep (UNSCH)

  - ICU/Core/Format/NumberFormat/NumberFormatSpecificationTest/TestScientificNotation (Rounding does not work with scientific notation.)

[http://bugs.icu-project.org/trac/ticket/11025] - tkeep

  - ICU/Core/Format/NumberFormat/NumberFormatSpecificationTest/TestPadding (Padding broken when used with currencies)

[http://bugs.icu-project.org/trac/ticket/11052] - yoshito

  - ICU/Core/Format/DateFormat/TimeZoneFormatTest/TestTimeRoundTrip (Ambiguous zone name - Samoa Time)

[http://bugs.icu-project.org/trac/ticket/11234] - scott

  - ICU/Core/Format/NumberFormat/NumberRegression/Test4212072 (Symbol roundtrip issues for locales ji, bm)

[http://bugs.icu-project.org/trac/ticket/9043] - pedberg UNSCH -> now 55.1, but depends on CLDR update

  - ICU/Core/Calendar/ChineseTest/TestFormat (Ambiguous Chinese era parsing)

[http://bugs.icu-project.org/trac/ticket/9503] - grhoten (duplicate, also mentioned earlier in this list)

  - ICU/Collate/RbnfLenientScannerTest/TestDefaultProvider (Lenient parse problems with English RBNF)

  - ICU/Collate/RbnfLenientScannerTest/TestEnglishSpellout

[http://unicode.org/cldr/trac/ticket/4375] - (CLDR) mark

  - ICU/Translit/Translit/RoundTripTest/TestDevanagariLatin

  - ICU/Translit/Translit/RoundTripTest/TestInterIndic

[http://unicode.org/cldr/trac/ticket/6745] - (CLDR) markus - low priority and non-trivial and want to keep the test

  - ICU/Collate/Collator/UCAConformanceTest/TestRulesNonIgnorable (UCARules.txt has problems)

[http://unicode.org/cldr/trac/ticket/7872] - (CLDR) agustin

  - ICU/Core/Util/ICUResourceBundleTest/TestLocaleDisplayNames (No localized region name for sah_RU, smn_FI)

2014/11/12

  1. CLDR 27 / ICU 55 schedule outline (from CLDR)

2014-12-10: CLDR 27 data structure change phase 1 (data structure locked)

    ICU integration 1 (starting 2014-12-10)

2014-12-17: ICU 55 milestone 1, CLDR data structure unlocked

     ICU integration 2 (starting 2015-02-14)

2015-02-21: CLDR 27 data structure freeze / ldml2icu converter

2015-03-07: CLDR 27 rc / data freeze / documentation for new data types

     ICU integration 3 (starting 2015-03-07)

2015-03-18: CLDR 27 final / ICU 55 rc

2015-04-01: ICU 55 release

  1. ICU 55 will have Unicode 7, possibly with the addition of a few high-priority characters if they are deemed stable (e.g., Emoji Fitzpatrick modifiers)
  2. Otherwise, Markus will work on Unicode 8 beta in branches
  3. ICU 56 (sep/oct) will pick up Unicode 8 (June)
  1. API Proposals for ICU 55
  2. Text break variants per locale identifiers (Peter) - FYI
  1. Specifying text break variants in locale IDs
  1. IncomingBugs * Reviews

2014/11/5 - No meeting (Intl Unicode Conference)

2014/10/29 - CLDR/ICU joint call for trac workflow discussion at 8am PT

  1. CLDR Trac Strawman - See this doc / discussion is captured in the doc.
  2. ICU Trac Workflow Problems doc

No regular ICU meeting

2014/10/22

  1. Trac workflow (Mark & Markus)
  1. CLDR Trac Strawman doc
  2. There are independent parts. Let’s try to make some progress on some of them.
  3. Since last time, added section “Mapping the strawman to the workflow”
  4. ICU Trac Workflow Problems doc
  5. CLDR discussion today:
  1. No agreement to replace actions with simple drop-downs
  2. Agreed to merged “assigned” & “accepted” states into “approved” (as in, committee approves to do this)
  3. Agreed to add “review-feedback” state
  4. Since we keep actions, keep a single “closed” state with resolutions
  1. Markus: “can we make similar (to CLDR) changes to ICU?”
  1. Yoshito: need api-needed http://bugs.icu-project.org/trac/ticket/11132 (also in https://docs.google.com/document/d/1j65S4naIlXkMxr-Y3pEdkspcXZTJlIsJVwJQMcCjS-o/edit#heading=h.dui34ctgmsew )
  2. Markus: call it “design” in ICU like in CLDR (usually means “API review”)
  3. reviewing -> feedback whether ± from the reviewer . Could mean “needs work” or “ready to integrate”.
  1. API Proposals for ICU 55
  2. IncomingBugs * Reviews
  3. Do we have a meeting next week? (Peter)
  4. CLDR workflow diagram:

2014/10/15

(Peter and Steven need to drop out at 11:00 PDT today; Andy & Mark are on vacation)

  1. ICU4J 54.1.1
  1. Published on Oct 9
  2. Updated release build instruction
  1. API Proposals for ICU 55
  2. IncomingBugs * Reviews

2014/10/08

  1. ICU 54 post-mortem
  1. Peter: Need more time between CLDR rc and ICU code freeze
  1. People resource issues
  2. Support for new features
  1. New ICU features depended on CLDR data that was not available until about code freeze
  2. a couple of versions ago we waited until CLDR nn.1 before ICU integration
  3. cldr data vs structure in milestones:
  4. Need to be integrating ICU support for new structure at same time it goes into CLDR to verify that the structure works
  5. Code reviews done too late to have intended effect
  6. Seed data often only in English, but should need to investigate data for other languages before adding structure, should be able to provide seed data in those languages (this is also a point for CLDR post-mortem)
  7. need to have the ICU support for new structure in order for CLDR to generate examples for Survey Tool usage
  1. CLDR: More formal process requirements for new structure proposals
  2. Reviews: Need to get reviews done earlier
  1. monitor “reviews by age” in weekly meeting
  1. Lighter-weight milestones (checkpoints) that don’t stop development for a week, and happen more often. Sync reviews up for each checkpoint.
  2. Use pre-submit reviews? At least for new APIs
  3. May need to tweak the workflow; Trac/svn prevents merging to trunk when the ticket is “fixed”. Maybe add status=reviewapproved?
  4. Consensus:
  1. Do pre-submit reviews.
  2. All new API on a branch, need to be reviewed before merging to trunk.
  3. Other large & complicated changes also on a branch.
  4. Can use Rietveld or similar rather than a branch.
  1. Known issues are starting to pile up; need a path to resolution (don’t carry for more than two releases).
  1. Keyword to flag which tickets correspond to known issues
  2. Some are in CLDR
  1. Some urgent CLDR problems identified (e.g. Hebrew RBNF). Errata / dot release?
  1. ICU 55 schedule
  1. API Proposals for ICU 55
  2. (Travis) Code review idea: checklists. Just as a pilot follows a preflight checklist before taxiing onto a runway for takeoff, so we developers should create and follow our own checklists when writing code. These same checklists can be used to review other’s code too. Here is an example checklist for C++. I can make a document and everyone can add common mistakes to it. Writing code is tough. Reviewing code is tough. Checklists help to make the job easier and to eliminate errors:
  1. IncomingBugs * Reviews 

2014/10/01

  1. ICU 54
  1. BRS
  1. post release binaries - done
  2. post updated docs - done
  3. update download page - done
  4. update main page - done except for summary
  1. 54 tickets