Michael Dyck wrote:
Unlike the current process, the post-ES2015 spec process requires two
shipping implementations before a feature is integrated into the spec.
While we're waiting for that, we anticipate proposal documents to
prepare for integration by being written as Ecmarkup/Ecmarkdown spec
deltas,

So not as git branches of the spec?

That might be better for significant cross-cutting changes, indeed.

/be
_______________________________________________
es-discuss mailing list
[email protected]
https://mail.mozilla.org/listinfo/es-discuss

Reply via email to