Branch or parallel directory for tests against ECMAScript 6.0 draft?

[tc39]

Branch or parallel directory for tests against ECMAScript 6.0 draft?

[bterlson]

The plan of record (which is open to change so feel free to push back) is that we will effectively move the entire tests/suite over to ES6, including ES6 organization. Running all ES5 tests will require checking out an older revision. Most ES5 tests are valid in ES6, they just need to be moved.

[ljharb]

That would be great provided there's a tag for it. If any updates need to be added, the tag can be moved.

[domenic]

A branch would make sense in that regard. Once the conversion work starts we can have es5 and es6 branches and then any changes to the es5 branch can be merged into the es6 branch.

[bterlson]

Created branch "es5-tests" based off of the last commit before I pulled in ES6 tests (and after I pulled in bug fixes). Cherry-picked deletion of external folder to save everyone some HDD space :)