Skip to content
This repository has been archived by the owner on Apr 12, 2024. It is now read-only.

Document that jqLite deprecations follow jQuery deprecation timeline #15282

Closed
Narretz opened this issue Oct 17, 2016 · 1 comment · Fixed by #15819
Closed

Document that jqLite deprecations follow jQuery deprecation timeline #15282

Narretz opened this issue Oct 17, 2016 · 1 comment · Fixed by #15819

Comments

@Narretz
Copy link
Contributor

Narretz commented Oct 17, 2016

Normally, once a feature is deprecated it will stay in the codebase for one minor release and will be removed in the next minor release (in Angular 1, minor releases are breaking release).

As discussed in #15221, we have decided to treat deprecations in jqLite which are directly related to corresponding deprecations in jQuery differently. Namely, the deprecated feature should not be removed, until jQuery removes it too (deprecated features tend to stay longer in jQuery than in Angular).

This decision should be documented in our FAQ.

@Narretz Narretz added this to the Backlog2 milestone Oct 17, 2016
@gkalpak gkalpak modified the milestones: Backlog2, Backlog Oct 18, 2016
@mgol mgol changed the title Put jquery deprecation strategy in the FAQ Put jQuery deprecation strategy in the FAQ Oct 31, 2016
@gkalpak gkalpak changed the title Put jQuery deprecation strategy in the FAQ Document that jqLite deprecations follow jQuery deprecation timeline Nov 26, 2016
mgol added a commit to mgol/angular.js that referenced this issue Mar 15, 2017
@mgol
Copy link
Member

mgol commented Mar 15, 2017

PR: #15819

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants