Planning/2.11: Difference between revisions
(Broken ARM machines) |
No edit summary |
||
Line 1: | Line 1: | ||
== Release Schedule == | == Release Schedule == | ||
NOTE! KVM Forum happens to be the week of 23-27, just before softfreeze, and some maintainers are likely to still be travelling between the end of that and the softfreeze date. If you're one of those people, or planning to try to get code in via their tree, make sure you get patches into trees and pull requests onto the mailing list early! | NOTE! KVM Forum happens to be the week of 23-27, just before softfreeze, and some maintainers are likely to still be travelling between the end of that and the softfreeze date. If you're one of those people, or planning to try to get code in via their tree, make sure you get patches into trees and pull requests onto the mailing list early! |
Revision as of 10:11, 2 November 2017
Release Schedule
NOTE! KVM Forum happens to be the week of 23-27, just before softfreeze, and some maintainers are likely to still be travelling between the end of that and the softfreeze date. If you're one of those people, or planning to try to get code in via their tree, make sure you get patches into trees and pull requests onto the mailing list early!
2017-08-31 | Beginning of development phase |
2017-10-31 | Soft feature freeze. Only bug fixes after this point. All feature changes must be already in a sub maintainer tree and all pull requests from submaintainers must have been sent to the list by this date. |
2017-11-07 | Hard feature freeze. Tag rc0 |
2017-11-14 | Tag rc1 |
2017-11-21 | Tag rc2 |
2017-11-28 | Tag rc3 |
2017-12-05 | Release, or tag rc4 if extra RC cycle needed |
2017-12-12 | Release, if we need an extra RC cycle |
Known issues
Please list all patch series or bugs which need to be fixed for the release here. That way I can be sure I don't miss any when I'm rolling release candidates.
Fixed in rc0
Not yet fixed in any rc
- The ARM machines smdkc210, nuri, raspi2, xlnx-ep108 and xlnx-zcu102 do not work anymore. Using them results in "tcg/tcg.c:538:tcg_register_thread: assertion failed: (n < max_cpus)"
Issues that will not be fixed
Targeted Features
See the ChangeLog/2.11 for full details.