Node.js Test CI Security Incident
Since Ember Data v1.0.0-beta.8, a lot has changed. Since we didn't write a blog
post for beta.8, this blog post will contain features in both beta.8 and beta.9.
Node.js Test CI Security Incident
If you've been following along, the Ember issues tracker has grown to over 200 active issues. While this is better than some other large OSS projects, it's still too large for us on the core team to easily keep track of. There are also a number of issues that are over six months old and even a year or two old.
Although most of our collaboration takes place on Github, IRC
(#emberjs
on freenode.net), and our Discourse site
the Ember.js Core Team meets privately every
Friday at 2pm EST/11am PST through Google Hangout for a weekly
discussion of all things Ember.
If you have a topic you'd like to see covered, contact your favorite
core team member and let them know!
Although most of our collaboration takes place on Github, IRC
(#emberjs
on freenode.net), and our Discourse site
the Ember.js Core Team meets privately every
Friday at 2pm EST/11am PST through Google Hangout for a weekly
discussion of all things Ember.
If you have a topic you'd like to see covered, contact your favorite
core team member and let them know!
Shortly after Ember 1.6.0 was released a regression was identified regarding custom error substates.
The error handling that was added to make debugging errors thrown in the Router's promise hooks
inadvertently caused the error substates to be completely ignored.
For more details review the following links: