You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The specs is the cornerstone for all the FD related software/data project. I think it's very important for any standard to define and publish as many governance details as possible. Probably the versioning is the most important at the current stage.
In my opinion, the versions of the specs should be very discrete (for example nov1.4.3) and well-emphasized in the docs. For example:
only v1 / v2 as in jsonschema - one release per a few years
something like ecmascript v2019 / v2020 - one release per year
I think it will not be possible to build a stable software eco-system on top of the specs if it changes too often.
The specs is the cornerstone for all the FD related software/data project. I think it's very important for any standard to define and publish as many governance details as possible. Probably the versioning is the most important at the current stage.
In my opinion, the versions of the specs should be very discrete (for example no
v1.4.3
) and well-emphasized in the docs. For example:jsonschema
- one release per a few yearsecmascript
v2019 / v2020 - one release per yearI think it will not be possible to build a stable software eco-system on top of the specs if it changes too often.
References:
The text was updated successfully, but these errors were encountered: