Update Breaking Changes doc for 2020-02-29 merge

This commit is contained in:
James Young 2020-01-04 12:24:51 -08:00
parent 6e520a721d
commit c1feeaa57f
No known key found for this signature in database
GPG Key ID: 918B32524640735F

View File

@ -10,16 +10,16 @@ The breaking change period is when we will merge PR's that change QMK in dangero
## When is the next Breaking Change? ## When is the next Breaking Change?
The next Breaking Change is scheduled for Nov 29. The next Breaking Change is scheduled for February 29, 2020.
### Important Dates ### Important Dates
* [x] 2019 Sep 21 - `future` is created. It will be rebased weekly. * [x] 2019 Sep 21 - `future` is created. It will be rebased weekly.
* [ ] 2019 Nov 01 - `future` closed to new PR's. * [ ] 2020 Jan 11 - `future` closed to new PR's.
* [ ] 2019 Nov 01 - Call for testers. * [ ] 2020 Jan 11 - Call for testers.
* [ ] 2019 Nov 27 - `master` is locked, no PR's merged. * [ ] 2020 Feb 26 - `master` is locked, no PR's merged.
* [ ] 2019 Nov 29 - Merge `future` to `master`. * [ ] 2020 Feb 28 - Merge `future` to `master`.
* [ ] 2019 Nov 30 - `master` is unlocked. PR's can be merged again. * [ ] 2020 Feb 29 - `master` is unlocked. PR's can be merged again.
## What changes will be included? ## What changes will be included?
@ -68,7 +68,7 @@ This happens immediately after the previous `future` branch is merged.
* [ ] `git push origin future` * [ ] `git push origin future`
* [ ] `git push --tags` * [ ] `git push --tags`
## 4 Weeks Before Merge ## 4+ Weeks Before Merge
* `future` is now closed to new PR's, only fixes for current PR's may be merged * `future` is now closed to new PR's, only fixes for current PR's may be merged
* Post call for testers * Post call for testers