1.0.0 Release

There were some notes, and plans about a 1.0 release. I want to use this issue for any discussion and plans around it and start a complete list of tasks to do before we can release.

There is this google doc that was started by @vojtajina and there was #944, which I will close in favor of this issue.

Below is an incomplete list of things that need doing in my opinion.

Organizational

• Clean up issue list (close outdated issues, respond to recent issues, and figure out which bugs are important enough to be fixed before release)
• Check for any api changes that need to be done before hand
• Bring all frameworks and launchers to a 1.0.0 ready state.
• Release 1.0.0 versions of the frameworks and launchers.
• Release 0.13.0 with the latest additions.
• Figure out how to handle peer dependencies (Ref https://github.com/npm/npm/issues/6565 and https://github.com/karma-runner/karma-phantomjs-launcher/issues/71) Ref: https://github.com/karma-runner/karma-phantomjs-launcher/issues/71#issuecomment-102834299 I don’t think we need to change anything about how we use peerDependencies.
• Fix release and merge process
• Update release process to handle proper semver and releases > 1.0
• Improve the official support situation (#1414)
• Make the canary build semver compatible (#1342)
• Enable github integrations on gitter
• Verify CLA process
• Remove cruft from canary branch and bring it up to date with master
• Remove iojs-1 from travis (ec4fa02 and d42802ad225ca81facdef565a4a121cb806bcc8a)

Improvements

• Update Socket.io to the latest version (PR #1404)
• Update all dependencies to their latest versions (PR #1410)
• Update all dev dependencies to their latest versions (PR #1279)
• Quality review the documentation
• Ensure support for node 0.10, 0.12 and io.js >= 2.0

Bugs

See the 1.0 Milestone

// cc @zzo @maksimr

Update: I updated the milestone to reflect relevant issues for this. Update2: Reorganize

[dignifiedquire]

It’s done 😃

[zzo]

do need to mention we can now go back and clean up module deps that have the ‘1.0 || xxxx’ syntax - this can be done as plugins &c actually need to be updated