Angular version support and ngx-avatars version schema
Heatmanofurioso opened this issue · 1 comments
This issue is to propose maintaining 2 baselines.
One supporting and maintaining the latest major Angular version, and one supporting the one before it.
As of now, that would involve supporting 12.x on one baseline and 13.x "as of tomorrow" on the other.
This shouldn't bring many issues apart from some API used in the project being deprecated and eventually removed, but even with that in mind, we will always have a large timeframe between deprecation and removal.
If this idea does go forward, one other step that would make sense to more easily make the library's versioning not seem confusing, would be to change the version schema to go side by side, at least on the major releases, with Angular's
EX: ngx-avatars:12.x.x and ngx-avatars:13.x.x
We've decided to implement this system, since there was no comment opposing it.
Major versioning is matching Angular's versioning