expected timeliness on glibc locale fixes

[Florian Weimer]

On 04/18/2016 08:10 PM, Mike Frysinger wrote:
> as we've been merging CLDR data in, a few claims have come up where
> the CLDR data is incorrect/out of date.  assuming CLDR is incorrect
> in these cases, how should we proceed ?  should we hot patch in the
> request, or wait for the wheels of the CLDR machinations to turn and
> then just pick up the next CLDR release ?  are there any cases where
> the values are so egregiously wrong that we feel "it must be resolved
> asap!" ?

Does CLDR have a public bug tracker, so that we can see what is coming 
down the pipe?

Florian