On Tue, Dec 06, 2016 at 03:13:51PM -0500, Matthew Miller wrote: > On Tue, Dec 06, 2016 at 09:11:06AM +0000, Daniel P. Berrange wrote: > > I expect we'd also rebase the virtualization stack in any .1 release, > > or even in the middle of a release if Fedora switched to a yearly > > major release cycle. 6+ months is already a long time to wait to push > > out new features to users, so making it longer is really not helpful > > from KVM virt stack pov. > > Would these updates just add new features or -- not counting accidental > regressions -- do they sometimes remove or change existing > functionality significantly? Would it be possible to reserve the latter > for the full release? As a general rule they'd always be adding new features. The only things that get removed as stuff users are not likely to hit (eg support for QEMU machine types that are 5+ years old which no one will seriously be running anymore) Regards, Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://entangle-photo.org -o- http://search.cpan.org/~danberr/ :| _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
