Bring @cycle/time to v1.0

[staltz]

Continuing from #578, there are a couple things to be done before cycle/time is official.

• [x] https://github.com/cyclejs/time/issues/37
• [x] https://github.com/cyclejs/time/issues/31
• [ ] Make time-related xstream operators become extra, in xstream (as a PR, and release candidate)
• [ ] Migrate cycle/time README.md to docs/content/api (as a PR)
• [ ] Update all official examples (also in the site) to avoid xstream time-related operators (as a PR)
• [ ] Update documentation/tutorial if it mentions time anywhere (as a PR)
• [ ] Merge those PRs mentioned above and release v1.0

[jvanbruegge]

I would add https://github.com/cyclejs/time/issues/29, because this will bring most likely some breaking changes for the architecture

[Widdershin]

Also including https://github.com/cyclejs/time/issues/31 as it is important to nail down first.

[Widdershin]

Opened #671 to implement extras.

@jvanbruegge I think we can do cyclejs/time#29 without breaking changes to the rest of the API, so it's my preference that we defer it until after v1.

I definitely still want to do it, but I want more time to discuss and consider the implementation without holding up the v1 release.

[IssueHuntBot]

@issuehuntfest has funded $60.00 to this issue. See it on IssueHunt