Katie Gengler

@locks I am looking at the tooling. It used to ignore the images (really need to figure out automated tests for workflows) @jenweber I think it is fine to merge...

@jenweber worth nothing you'll have to open the advancement PR yourself using https://github.com/emberjs/rfcs/blob/master/.github/READTHIS.md#trigger-opening-advancement-pryml

Closing since it contradicts the RFC

As @wycats said, we don't want to change Ember.Object at this point. Ember projects in general should be moving to native classes. Since this has had no movement in two...

I'm going to go ahead and close this -- this was unspecified behavior and not an area we want to touch going forward.

Is this still relevant?

@RobbieTheWagner Have you seen https://github.com/emberjs/ember.js/issues/19492 and https://github.com/emberjs/ember.js/issues/19493 ?

Closing in favor of https://github.com/emberjs/tracking-polaris/issues/31

Is this still relevant?

As we plan to rework the router for Polaris, we're hesitant to touch existing router code (every bug we fix is one someone else relies upon).