removing bound scope properties on destroy

[moschel]

By the time the destroy event of a component is run, the bound scope properties are no longer bound to their parent component properties. In other words, if you pass a cross bind a scope property from a parent to child component like:

<my-component product="{product}"></my-component>

Then you want to clean up that product reference while the component is destroyed like:

events: {
  destroyed: function(){
    this.scope.attr('product', null);
  }
}

This won't throw an error, but the product property of the parent component won't be affected by this, because the property bindings are unbound before destroyed is called. I think we should change the order so the bindings are cleaned up after destroyed is called.

[moschel]

@daffl can't we close this?

[daffl]

No. Referenced issues will be closed automatically once in master.

[justinbmeyer]

We can close them before that if they are in minor. Too bad github doesn't have some setting like this.

[daffl]

We could make minor the default branch. I don't think that finding all the still open but referenced issues in merged PRs against minor is necessary though. I'd also rather have people watching an issue be notified if a new release has been made not just if the fix made it in a development branch.