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

Suggest to follow Angular Support Policy and Schedule (LTS support) #2627

Open
turnerguo opened this issue Dec 13, 2018 · 3 comments
Open

Suggest to follow Angular Support Policy and Schedule (LTS support) #2627

turnerguo opened this issue Dec 13, 2018 · 3 comments
Assignees
Labels
📋 Backlog 💬 Discussion Need more insights to this issue

Comments

@turnerguo
Copy link

What problem does this feature solve?

To be a production ready library, it is necessary to have a LTS version for better enterprise level usage.
Currently, NG-ZORRO just has a straight branch line (master), so it is not able to support any special version for some reason.
Since version 7 NG-ZORRO start to track the major version of @angular/core, I think it also good to keep follow the Angular Support Policy and Schedule (https://angular.io/guide/releases#support-policy-and-schedule).

What does the proposed API look like?

Follow the Angular Support Policy and Schedule: https://angular.io/guide/releases#support-policy-and-schedule 👋
e.g. create branches for each major version (just like v6.x.x), and give V6 LTS support follow the above.

@wzhudev wzhudev added the 💬 Discussion Need more insights to this issue label Dec 13, 2018
@turnerguo
Copy link
Author

We even don't know where is the BREAKING CHANGES point with different Angular versions.
No one care about this? just happy to running on the latest version? 😢

@vthinkxie vthinkxie mentioned this issue Feb 19, 2019
12 tasks
@vthinkxie vthinkxie self-assigned this Feb 26, 2019
@lppedd
Copy link
Contributor

lppedd commented Jun 10, 2019

@turnerguo Imho there is no point in having a LTS release. This isn't a massive project, it is open-source, you're able to see issues, to try it out and downgrade if necessary.

As part of my daily task I have a scheduled npm update. If things breaks, nevermind, rollback. The test/quality environment is there for this.

Instead, we should strive for even faster release cycles, if possible.

@wzhudev
Copy link
Member

wzhudev commented Aug 8, 2019

IMHO, it is unnecessary to maintain LTS versions for the following reasons:

  1. It is easy for developers to update to a new major version. Angular provides a tool for that ng update. Take our business product (which uses ng-zorro-antd, of course) for an example, there are 80,000 lines of code and it only took me a morning to update from 7 to 8. So the benefit of LTS is limited.
  2. It would takes a lot extra efforts to maintain different branches. We have to double or even triple reproductions, pull requests and coding. But we are a small team of 5 active members and we have no time for that, which I am pretty sure. 🤣

In conclusion, 💰> 🎉.

BTW, the official component library Material doesn't provide LTS, either, according to the version history on npm.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
📋 Backlog 💬 Discussion Need more insights to this issue
Projects
None yet
Development

No branches or pull requests

4 participants