Formalize plan for ECMA-402 updates dependent on UTS 35 #584
Labels
c: spec
Component: spec editorial issues
s: help wanted
Status: help wanted; needs proposal champion
Milestone
In several issues recently, including #183, #437, and #581, we've made updates to ECMA-402 as a reaction to an update in UTS 35. Currently, the plan of action is to perform these updates on an ad-hoc basis. I would like the editors to discuss a sustainable plan as a path forward and document it.
The text was updated successfully, but these errors were encountered: