docs: add v23 release and change to yearly release cycle#69817
docs: add v23 release and change to yearly release cycle#69817thesmiler wants to merge 1 commit into
Conversation
## Summary This PR adds v22.x and v23 release dates. It also changes Angular's release cadence to a yearly cycle. ## Why we are making this change The community has long requested less frequent major releases due to the impact of breaking changes and upgrades for their projects as well as for enterprise customers. Additionally, a longer release cycle provides increased API stability for developers using agentic workflows, while still delivering a reasonable cadence of API upgrades and migrations.
|
Deployed adev-preview for 37afb54 to: https://ng-dev-previews-fw--pr-angular-angular-69817-adev-prev-9womvemj.web.app Note: As new commits are pushed to this pull request, this link is updated after the preview is rebuilt. |
|
Does it imply that you will still introduce experimental and/or development previews in minor releases? Before the advent of the LLM era, upgrading to Angular’s latest version was already quite straightforward. Now, it’s easier than ever. |
|
I feel like this change is more like for AI's be able to reach the knowledge of the current version more than the developers/mantainers. If the new major version requires alot of breaking changes will this not cause that frameworks that build on angular to take twice as much more time to adapt to the new version? I hope this does not becomes the fiasco of .net framework being a torture to update from a version to another just because each version are just to many breaking changes. |
Major releases were really only meant to introduce breaking changes. Minor release were already used to introduced new features (stable or experimental/dev preview). |
JeanMeche
added
action: merge
|
Recent major upgrades have been genuinely painless - less because of cadence and more because of the automatic migration schematics and the deprecation policy spreading changes across releases. So the upgrade-burden rationale alone wouldn't obviously justify this change. One thing the announcement leaves open: should the slower major cadence be read as a signal about the level of investment in Angular going forward, or is team capacity unchanged and this purely about reducing ecosystem churn? Given the stated rationale explicitly targets agentic workflows and the AI ecosystem moves on a monthly cadence, sustained feature velocity in minors (e.g. iteration on experimental features like WebMCP) matters more than ever - so an explicit statement on investment would help teams making long-term framework bets. edit: updated, as question was partly answered already. |
|
Part of me wishes we'd waited for v29 in late 2029 to align Angular versions with the calendar year. |
|
Perfectly confirms my previous point. I used to be an assistant developer for Angular, but now I am very disappointed in Angular, and I can feel that you have lost the passion to maintain this project. |
|
You should definitely label the next major by the year it's released in, even if you jump a couple majors. |
It's totally fine to be disappointed with changes. But I think it's unfair to say that the passion is lost. The Angular team is doing a great job. Amazing features are being shipped all the time. And also there are many community PRs coming in every single day. So I think the passion for sure is here. Besides, Angular is used in 3000+ Google apps such as Gemini and Google Fonts so I think Angular project will be maintained 😁 |
This comment was marked as abuse.
This comment was marked as abuse.
This comment was marked as abuse.
This comment was marked as abuse.
|
I'd like to remind commenters that the https://github.com/angular/angular/blob/main/CODE_OF_CONDUCT.md applies here. Thank you. |
|
It would be nice to have the major version coincide with the current year |
|
It would be great to see fewer breaking changes in patch versions as well. I’ve had a lot of issues with SSR breaking in v20 with patch updates. It may be our codebase but the upgrade schematic has never worked for me. I always have to do it by hand. |
Those were all related to important security fixes. |
After v23 released |
15 participants
Summary
This PR adds v22.x and v23 release dates. It also changes Angular's release cadence to a yearly cycle.
Why we are making this change
The community has long requested less frequent major releases due to the impact of breaking changes and upgrades for their projects as well as for enterprise customers. Additionally, a longer release cycle provides increased API stability for developers using agentic workflows, while still delivering a reasonable cadence of API upgrades and migrations.
This PR will not affect how features are released in general, features can and will continue to be shipped in minor versions. Only breaking changes are restricted to major versions.