After Angular 2 programmers are now looking for angular 4 release date for more features and more powerful language. No doubt angular is becoming most popular and powerful front end client side language for single page applications. It is also consider mobile first approach.

The First Angular conference NG-BE, Belgium’s was conduct at 9th of December 2016. The Angular lead developer Igor Minar attended the conference as the keynote speaker. They have some interesting announcements about Angular’s release schedule. Here couple of important things & announcement, please read the entire post and watch video below. Thanks

Igor Minor Tweet on 9th December:

Angular 4 Releases Date

Angular 4.0 will be released in march 2017 so ready for more features of angular 4 for building single page mobile & web applications.

Why Angular 4? and Why not Angular 3? What’s going on?

Use of  SEMANTIC VERSION in Angular:

The angular team already told when the Angular 2 finally released back in September, that they will switch to Semantic Versioning (SEMVER) of angular.

The Semantic Versioning is nothing, just all about increasing(adding) version numbers of angular. This enable angular developers to not only reason about any upgrade we do, but we can even let tools such as NPM do it in a automatic and safe manner for us.

A semantic version of angular consists of three numbers see in picture below:

angular-4.0-semantic-versions

 

It’s just “Angular”

As you might have already guessed, the term “Angular 2” is also kind of deprecated once we get to version 4, 5 etc. That said, we should start naming it simply “Angular” without the version suffix.

“It’s just #angular”

Also, we should start avoiding GitHub/NPM libraries prefixed with ng2- or angular2-.

Naming guidelines

Basically from now on, name all versions of Angular simply “Angular”. Try to avoid using the version number, unless it is really necessary to disambiguate.

Three simple guidelines:

  • Use “Angular” by default (e.g. “I’m an Angular developer”, “This is an Angular meetup”, “The Angular ecosystem is growing quickly”)
  • Use “Angular 1”, “Angular 2”, “Angular 4” when talking about a specific release train (e.g. when talking about a newly introduced feature – “This is an introduction to feature X, introduced in Angular 4”, “We are upgrading from Angular 1 to Angular 2”, “I’m proposing this change for Angular 5”)
  • Use full semver version when reporting a bug (e.g. “This issue is present as of Angular 2.3.1”)

 

Why version 4 Instead of 3 ?

Angular js core libraries live in one single GitHub repository at github.com/angular/angular. All of them are versioned the same way, but distributed as different NPM packages:

angular2-all-versions

Due to this misalignment of the router package’s version, the angular team has been decided that they were go straight for Angular v4. This is because all core packages will be east to maintain and bye this way it help to avoid confusion in the future.

Tentative release schedule

The fact that breaking changes will arrive, doesn’t mean they will arrive every other week. The Angular team committed to time based releases that occur in three cycles:

  1.  every week patch releases,
  2. after each major release, 3 monthly minor release
  3. a major release with easy-to-migrate-over breaking changes every 6 months.

The next 3 months will be dedicated to finalizing Angular 4.0.0.

angular4-schedule-tentative

After Angular 4.0.0, the tentative schedule for further releases of angular is fellow below:

Predictable, Transparent & Incremental Evolution(Angular Latest and Future release version and dates)

Version No.   Release Date

  • Angular 4          4 March 2017
  • Angular 5          September/October 2017
  • Angular 6          March 2018
  • Angular 7          September/October 2018 

angular-lastest-future-releases

Watch Angular 4 announcement Video Yourself

Conclusion:

If we analysis the entire post and facts then we can There are two main important messages here:

  • You do not need to worry about version numbers of angular.
  • we do need to evolve Angular in order to avoid another Angular 1 to Angular 2 change, but we should do it together as a community in a transparent, predictable and incremental way.

Also, I’d like to thank Igor for being so open at presenting this data, especially since he knows what a sensitive topic breaking changes are and have been in the past. This means a lot and I hope that the community will realize why all these changes are good for everyone involved.