Angular 1.x support timeline announcement is direly needed.

[sebastian-zarzycki-apzumi]

We have many clients that asks us about the expected support dates and there's no single reliable resource we can point them to. There are various inconclusive information scattered around the internet.

This increases the reluctance to use Angular (whether 1 or 2+) in new projects.

Obviously, there's a hidden wish that business would migrate early to 2+, but it cannot be achieved by lack of information.

[Narretz]

Can you elaborate what exactly you need to know? Do you mean security updates?

[sebastian-zarzycki-apzumi]

Security and compatibility (with browsers), yes.

Basically, I observe a trend where new clients are concerned that the "support" for Angular 1.x will end soon, which could put their projects in jeopardy in near future. What they exactly mean by "support" is not that relevant, as long as it is backed by some kind of official announcement. Currently there is no clear statement in this regard and it is generally perceived as a sign of imminent project abandonment. Clients need to understand whether their Angular 1.x project is relatively "safe" in the timespan of 12-24 (or more) months.

[Narretz]

Even if the project was abandoned this would not mean that the projects stop working. Wrt browser support. There will be no changes to the bottom end support. For current browser we will evaluate changes for modern APIs but since there are no BC for new Javascript versions there is nothing to worry about. I will bring this topic up in the next meeting

[sebastian-zarzycki-apzumi]

As a developer I understand that and I don't expect Angular 1.x to "break" anytime soon, even if no new versions are released. But for business, they really tend to rely on these "official statements" and I think Angular community would benefit from one, one way or another.

Simply, the statements made until now (about the traffic majority and whatnot), are not precise enough for business to rely on.

So, that said, I would be grateful for bringing this up and if that could result in some kind of statement, it would mean a lot.

[tommck]

Yeah, I'm on a large angular 1.X project that's not production yet, but this will be in existence for a LONG time (large Enterprise). It would be interesting to have any extra information in this vein

[Narretz]

While there's nothing substantial yet, the Angular team is aware of this and there will definitely be more concrete info about this. I'm closing this issue in the meantime.

[jrvidal]

@Narretz Thanks for the response. It would be nice to leave a notice here of said info when it's available, for whoever is already tracking this issue.

[sellmeadog]

Not sure if this is the appropriate place for this comment, but I also work for a large enterprise with a significant investment into Angular 1.x and we are now starting a large system integration project that will deliver numerous enhanced UI projects. I am trying to encourage the adoption of Angular 2.x for these efforts but without a published support roadmap, there is no desire from the team to upgrade and retrain the development staff on the new framework. Any type of official service life roadmap for 1.x would go a long way in pushing for the adoption of 2.x and beyond.

[robwormald]

@sellmeadog we're not ready to make any official announcements as of yet, but that specific feedback is definitely useful for our planning, thanks!

[slagod]

Guys, why you close the issue without providing information? You cannot announce anything now - that's fine, but I think you should leave the issue open until announcement is made.

[RubyRabelle]

I am also confused about this. I have been researching for several months, with the impression that development was essentially over (stable) for AngularJS in favor of Angular2 (or 4?), and now 1.6.5 has been released and I'm seeing discussions about 1.7. What direction is this project going?