# Ok.. let me explain: it's going to be Angular 4.0, or simply Angular

DevFeed: [Ok.. let me explain: it's going to be Angular 4.0, or simply Angular](<https://devfeed.tech/articles/ok-let-me-explain-it-s-going-to-be-angular-4-0-or-simply-angular-21308.md>)

Original publisher: [Read original article](<https://juri.dev/blog/2016/12/let-me-explain-angular-release-cycles/>)

Published: 2016-12-12T00:00:00Z

Content type: article

Language: en

Sources: [Juri Strumpflohner](<https://devfeed.tech/sources/juri-strumpflohner.md>)

Topics: [Angular](<https://devfeed.tech/topics/angular.md>), [upgrade](<https://devfeed.tech/topics/upgrade.md>), [npm](<https://devfeed.tech/topics/npm.md>), [TypeScript](<https://devfeed.tech/topics/typescript.md>)

Tags: [angular](<https://devfeed.tech/tags/angular.md>), [npm](<https://devfeed.tech/tags/npm.md>), [upgrade](<https://devfeed.tech/tags/upgrade.md>), [versioning](<https://devfeed.tech/tags/versioning.md>)

## AI overview

This article explains Angular's release-cycle and versioning decisions, including why the project moved to Semantic Versioning and why Angular 4 was announced after Angular 2. It describes how bug fixes, new features, and breaking changes affect version numbers and upgrades.

## Source excerpt

Lorem ipsum dolor sit amet