Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

I don’t think we need this anymore. #2887

Merged
merged 1 commit into from
Jan 5, 2015
Merged

Conversation

stefanpenner
Copy link
Contributor

maybe we do..3a439e1#diff-f1e1923c0440a385f51d2a81c0e53b64R63

But I would like to get a path forward, were we don't need this.

If this is merely going to be a breaking change for add-ons then we will doit, and bump the version accordingly.

Also if this is something we want to support, we need proper test coverage.

@stefanpenner stefanpenner force-pushed the remove-old-dep branch 2 times, most recently from 249b1ab to be6f26b Compare January 4, 2015 23:36
@rwjblue
Copy link
Member

rwjblue commented Jan 4, 2015

I think its fine to remove, as long as we have a [BREAKING] tag in the changelog (under the addon section). I do not think this warrants a 0.2.x version bump (I am not aware of addons actually using this).

stefanpenner added a commit that referenced this pull request Jan 5, 2015
I don’t think we need this anymore.
@stefanpenner stefanpenner merged commit b612771 into master Jan 5, 2015
@stefanpenner stefanpenner deleted the remove-old-dep branch January 5, 2015 00:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants