honeymoose
/
angular-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
angular-cn/docs/RELEASE_SCHEDULE.md

86 lines
6.1 KiB
Markdown
Raw Normal View History

docs(release-schedule): add release schedule doc (#13827) While authoring this document we agreed to pushing off the 4.0.0 release by one week by adding one more RC week (compared to the original plan). We announced that RC would take 1 month, but then I did the calendar math incorrectly. This schedule change will give community more time to test the release before we call it done and report any potential regression or unforeseen issues.
2017-01-11 16:22:50 -05:00
# Angular Release Schedule
This document contains historic record of past Angular releases and future release schedule.
The purpose of this document is to assist coordination among the Angular team, Angular contributors, Angular application teams, and Angular community projects.
We'll keep this doc up to date when unplanned releases or other schedule changes occur.
## Schedule Caveats and Exceptions
The dates listed here are approximate – last minute issues, team or community events, etc. can cause us to release a few days sooner or later.
This page contains only planned and past unplanned releases.
Due to serious regressions or other important reasons we reserve the right to release an unplanned patch or minor release.
In such case, we'll update this document accordingly.
The dates past March 2017 are just a guidance and might be adjusted slightly if necessary.
## Tentative Schedule Until March 2017
<!--
The table below is formatted so that it's easy to read and edit in both markdown and rendered html form.
In order to deal with undesirable line breaks, two special characters are occasionally used:
- non-breaking hyphen: "‑" http://www.fileformat.info/info/unicode/char/2011/index.htm
- non-breaking space: " " http://www.fileformat.info/info/unicode/char/00a0/index.htm
If you see undesirable wrapping issues in the rendered form, please copy&paste the quoted characters and use them in the table below where needed.
-->
Week Of | Stable Release<br>(@latest npm tag) | Beta/RC Release<br>(@next npm tag) | Note
------------- | ----------------------------------- | ---------------------------------- | ---------------------
2016-09-14 | 2.0.0 | - | Major Version Release
2016-09-21 | 2.0.1 | 2.1.0-beta.0 |
2016‑09‑28 | - | - | Angular Connect
2016-10-05 | 2.0.2 | 2.1.0-rc.0 |
2016-10-12 | 2.1.0 | - | Minor Version Release
2016-10-19 | 2.1.1 | 2.2.0-beta.0 |
2016-10-26 | 2.1.2 | 2.2.0-beta.1 |
2016-11-02 | 2.1.3 | 2.2.0-rc.0 |
2016-11-09 | 2.2.0 | - | Minor Version Release
2016-11-16 | 2.2.1 | 2.3.0-beta.0 |
2016-11-23 | 2.2.2 | 2.3.0-beta.1 |
*2016-11-23* | *2.2.3* | - | *Unplanned Patch Release to fix regressions*
2016-11-30 | 2.2.4 | 2.3.0-rc.0 |
2016-12-07 | 2.3.0 | - | Minor Version Release
2016-12-14 | 2.3.1 | 4.0.0-beta.0 |
*2016-12-21* | *2.4.0* | - | *Unplanned Minor Release due to release of RxJS 5.0.0*
2016-12-21 | 2.4.1 | 4.0.0-beta.1 |
2016-12-28 | - | - | Holiday Break
2017-01-04 | 2.4.2 | 4.0.0-beta.2 |
2017-01-11 | 2.4.3 | 4.0.0-beta.3 |
2017-01-18 | 2.4.4 | 4.0.0-beta.4 |
2017-01-25 | 2.4.5 | 4.0.0-beta.5 |
2017-02-01 | 2.4.6 | 4.0.0-beta.6 |
docs: add 4.0.0-beta.7 to the release schedule (#14341) I messed up and accidentaly led the team to believe that the feature freeze was on Feb 15. Because of this most work was planned to be done by Feb 15 and there is no way to finish it by the original date of Feb 8. To remedy this situation we agreed to add one more beta to the release schedule.
2017-02-07 12:45:33 -05:00
2017-02-08 | 2.4.7 | 4.0.0-beta.7 |
docs: update schedule by adding one more beta (#14494) The new view engine is behind schedule. We agreed to slip the release by one more week.
2017-02-15 00:42:38 -05:00
2017-02-15 | 2.4.8 | 4.0.0-beta.8 |
docs: update release schedule due to bad 4.0.0-rc.0 release
2017-02-24 21:08:28 -05:00
*2017-02-22* | | *4.0.0-rc.0* | *Unplanned release: bad rebase*
docs: update 2.4.9 release schedule
2017-03-02 01:43:38 -05:00
2017-02-22 | | 4.0.0-rc.1 | No stable release - we were too busy with the RC
2017-03-01 | 2.4.9 | 4.0.0-rc.2 |
2017-03-08 | 2.4.10 | 4.0.0-rc.3 |
2017-03-15 | 2.4.11 | 4.0.0-rc.4 |
2017-03-22 | 4.0.0 + 2.4.12 | - | Major Version Release
docs(release-schedule): add release schedule doc (#13827) While authoring this document we agreed to pushing off the 4.0.0 release by one week by adding one more RC week (compared to the original plan). We announced that RC would take 1 month, but then I did the calendar math incorrectly. This schedule change will give community more time to test the release before we call it done and report any potential regression or unforeseen issues.
2017-01-11 16:22:50 -05:00
## Tentative Schedule After March 2017
Date | Stable Release | Compatibility`*`
---------------------- | -------------- | ----------------
September/October 2017 | 5.0.0 | ^4.0.0
March 2018 | 6.0.0 | ^5.0.0
September/October 2018 | 7.0.0 | ^6.0.0
`*` The goal of the backwards compatibility promise, is to ensure that changes in the core framework and tooling don't break the existing ecosystem of components and applications and don't put undue upgrade/migration burden on Angular application and component authors.
## More Info & Resources
In [September 2016 we announced](http://angularjs.blogspot.com/2016/10/versioning-and-releasing-angular.html) that Angular is fully adopting [semantic versioning](http://semver.org/) and that we'll be releasing patch versions on a weekly basis (~50 per year), minor versions monthly for 3 months following a major version release, and every 6 months we'll release a major version that will be backwards compatible with the previous release for most developers, but might remove APIs that have been deprecated two major versions ago (6 or more months ago).
In [December 2016 we clarified this message](http://angularjs.blogspot.com/2016/12/ok-let-me-explain-its-going-to-be.html), and provided additional details about the plans to release Angular 4.0.0 in March 2017.
This document contains updates to the schedule that happened since then.