Planning/2.1: Difference between revisions
No edit summary |
No edit summary |
||
| Line 30: | Line 30: | ||
|- | |- | ||
| <strike>2014-07-24 or -25</strike> 2014-07-29 | | <strike>2014-07-24 or -25</strike> 2014-07-29 | ||
| Tag v2.1.0-rc4 | | Tag v2.1.0-rc5 (there was a bug found and fixed after tagging of -rc4 but before tarball creation so for practical purposes we skipped the rc4) | ||
|- | |- | ||
| <strike>2014-07-29</strike> 2014-08-01 | | <strike>2014-07-29</strike> 2014-08-01 | ||
Revision as of 16:54, 29 July 2014
Release Schedule
| 2013-04-17 | Beginning of 2.1 development phase |
| 2014-05-17 | Mid-point of development cycle |
| 2014-06-17 | Soft feature freeze. All features
should have patches on the list by this date; major features should have initial code committed. |
| 2014-07-01 | Hard feature freeze. Tag v2.1.0-rc0,
only bug fixes committed after this point |
| 2014-07-08 | Tag v2.1.0-rc1,
PCI/PC/VIRTIO/VHOST: only high priority fixes from here on. high priority means regression fixes or fixes in a new feature if there is no workaround. |
| 2014-07-15 | Tag v2.1.0-rc2 |
| 2014-07-22 | Tag v2.1.0-rc3 |
| Tag v2.1.0-rc5 (there was a bug found and fixed after tagging of -rc4 but before tarball creation so for practical purposes we skipped the rc4) | |
| Tag v2.1.0 |
Known issues
- rc1 may fail a string output visitor test
Also see Planning/2.1/Testing.
Targeted Features
See the ChangeLog/2.1 for full details.