Roadmap for 1.0.0

e-c’s been stable for a while, probably time to make it 1.0.0. Here’s some things I’d like to try and address before then (and please feel free to comment and link to important not-yet-addressed existing issues):

• Better testing solution / methodology for timer loops and slow timers, possibly involving ember-milestones
• (possibly) changing the behavior of error handling: it’s really crappy that we populate the .error field on the task instance AND we still bubble the error out of the run loop. Error handling is hard but it’s one of the dumber behaviors/apis in e-c
  • proposals/idea: Selective error bubbling
  • pattern: marking error as handled, ignored in Ember.onerror
• fix waitFor* not working with race() and other promise helpers

…and many more (i think): please help me fill this out.

[bartocc]

+1 on error handling. I am often confused about how to use the try/catch blocks with my tasks

[jrjohnson]

This is a great list, but I’d like to put a vote up for declaring 1.0 right now and addressing these as time permits possibly for 2.0 if they are breaking. Or 3.0, or 4.0 😜

Tons of apps and addons are using this in production now which points to it’s stability and the reasonableness of a 1.0 designation, but it also makes it a primary source of conflicts for us when using ember-cli-dependency-lint.

The reason is that an addon which declares "ember-concurrency": "^0.8.0", needs to be updated for 0.9 and 0.10, whereas declaring "ember-concurrency": "^1.0", would allow NPM to just resolve these conflicts automatically giving the latest version in most cases.