search

MicrosoftEdge / Status

This repository tracks the roadmap for the Microsoft Edge web platform. This data is used on https://status.microsoftedge.com/ to provide implementation status and forward-looking plans for web standards in Edge and other browsers.
https://status.microsoftedge.com
Other
534 stars 200 forks source link

Update ES6 entries to point to final spec #244

Open jacobrossi opened 9 years ago

jacobrossi commented 9 years ago

Correct link: http://www.ecma-international.org/ecma-262/6.0/

But we should do the correct hash navs to the individual features. @bterlson do you have time to put up a PR for this?

domenic commented 9 years ago

How do you guys feel about removing the " (ES6)" suffix? It seems redundant with the categorization of them as JS. And then there's the misleading "ES7" suffix, which is just incorrect since ES7 doesn't exist and nobody knows what features will be included in it.

Not to mention 6 vs. 2015 and 7 vs. 2016.

jacobrossi commented 9 years ago

It's there primarily for searchability (the filter on the left works against the feature titles). Also, the site has a flaw that changing the title changes the URL to that feature (doh, eventually would like to fix this). We should though just go ahead and move ES7 to ES 2016 probably, since the searchability thing probably only applies to ES6 since it's a well-used term at this point.

domenic commented 9 years ago

Well, you should remove any reference to future ES versions, since we don't know what's going to be in them. E.g. no idea if SIMD is ES7 or ES8 or ES9 or never gonna happen.

bterlson commented 9 years ago

I felt bad adding ES7/ES2016 qualifiers but I felt it was valuable to distinguish between features in ratified specs and those that are upcoming. @Domenic what do you think about adding a generic ES.next qualifier? Presumably this would be most valuable if we and Chrome agreed on a qualifier :)

domenic commented 9 years ago

Not "next", but maybe "ES proposal"?

bterlson commented 9 years ago

Proposal may confuse people who expect to see stage 2 = draft, stage 3 = candidate, etc. It would be nice actually to reflect the actual spec stage (so ES proposal, ES draft, ES candidate draft, ES final draft) but then it's a burden on me to update status as the proposals move through the process. But maybe that's ok - thoughts?

domenic commented 9 years ago

I mean, I think they're all proposals, of various stages. If you're up for transcribing the statuses, that's cool, but just proposal seems fine and not confusing to me.

bterlson commented 9 years ago

I'm fine with ES Proposal. @jacobrossi does this seem like a reasonable qualifier to you? If so I can replace ES7/ES2016 with ES Proposal across the board.

jacobrossi commented 9 years ago

There is a field explicitly to denote standards status (from Proposal > Editor's Draft > Working Draft or Equivalent > Established Standard). But if "ES7" is an issue, changing that to "ES Proposal" seems reasonable to me. Happy to merge a PR for that.

domenic commented 9 years ago

Don't get me started on that field :sob: