[Unicode]   Common Locale Data Repository : Bug Tracking Home | Site Map | Search

CLDR Ticket #7689(accepted defect)

Opened 4 years ago

Last modified 3 years ago

Don't leave vetting until we are at 100% modern coverage

Reported by: mark Owned by: srl
Component: survey Data Locale:
Phase: dsub Review:
Weeks: Data Xpath:


Right now, we (and administrators) can't easily see that modern coverage items (for the CLDR Modern Locales) are missing. We can generate the chart with ShowLocaleCoverage, but we run it after the end of vetting, which makes it then a pain to fix the outlying items (about 970 this time).

Those also affect the error counts, because of the missing items in logical groups.


Make these easy for everyone to see, and don't leave vetting until we are at 100%.


Change History

comment:1 Changed 4 years ago by emmons

  • Status changed from new to assigned
  • Component changed from unknown to survey
  • Priority changed from assess to critical
  • Milestone changed from UNSCH to 27dvet
  • Owner changed from anybody to srl
  • Type changed from unknown to defect

comment:2 Changed 4 years ago by mark

  1. Change error reporting to be exactly the same for VETTING and post-VETTING
  2. Make clear to users exactly what the status is in the dashboard
  3. Have a dashboard for the committee that shows the status for us.
  4. Every day during the last week of vetting, review #3 and send messages to the failing locales.

comment:3 Changed 4 years ago by markus

  • Phase set to dvet
  • Milestone changed from 27dvet to 27

comment:4 Changed 3 years ago by srl

  • Milestone changed from 27 to 28


comment:5 Changed 3 years ago by srl

  • Status changed from assigned to accepted

comment:6 Changed 3 years ago by emmons

  • Phase changed from dvet to dsub
  • Milestone changed from 28 to 29

Moving all survey related to 29dsub

comment:7 Changed 3 years ago by emmons

  • Milestone changed from 29 to upcoming

Automatic move of all 29 -> upcoming


Add a comment

Modify Ticket

as accepted

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.