Tom Bishop

@srl any update on this? BRS "Upgrade server" points to CLDR-15176 which is related to this

@srl295 "This PR has undefined commits"? not sure what that means -- and is this something we should test locally before approving?

@srl295 i don't remember the "strange XML test behavior" -- anyway, testing locally, 2.12.2 seems fine for me so far... we want to link this PR to https://unicode-org.atlassian.net/browse/CLDR-15319 right? should...

"Commit message for 7600d13 fails validation" -- what's actually wrong with the message, and where's the validation code?

> Where you had to rebase the snapshot PR to make it pass Ah, the infamous "Duplicate: hi_Latn.xml"!

great! I'll focus on why the test fails, and possible ways to make it pass

@macchiati @srl should we revisit this draft pr by Mark? it's connected to a major-stretch ticket, but might it be valuable for the current blocks-progress inheritance tickets under https://unicode-org.atlassian.net/browse/CLDR-16537 ?

@srl295 it's not clear to me that CheckDisplayCollisions tests uniqueness of annotations. It has: `else if (CHECK_FLAG_AND_EMOJI && myType == Type.ANNOTATIONS)` but CHECK_FLAG_AND_EMOJI is false. What's the basis for thinking...

Interesting! It would help to have more concrete examples of how we would use this. One thing that's not clear to me is what are the pros/cons of configuring this...

If it has to be squashed into a single line it might be a little cumbersome: CLDR_FE_DEBUG={someProperty:true, anArray: [4,5,6], CLDR_TABLE_DEBUG: true, DEBUG_SHOWER: false, DEBUG_LOCALE_STAMP: false, CLDR_VOTE_DEBUG: false, ...}