Hi,

Sorry for the short notice of this email.

the state of branch ovirt-3.6 is as follows

tag     sha     subject                                                         
        bug             target release  
----------------------------------------------------------------------------------------------------------------------
        de54e59 virt: Don't expose GuestAgent.guestInfo directly                
        1295428         3.6.3
        83c4ac8 supervdsm: failed validateAccess leaves pipes open              
        1271575         3.6.3
        37bda50 vm: safer handling of conf in restore                           
        1296936         3.6.3
        57b1814 virt: safer handling of migration parameters                    
        1296936         3.6.3
        9b29ddd lun: Serial attr should not passed to libvirt for lun disks.    
        1291930         3.6.2 <<<<
        7b94531 migration: use context manager for semaphore                    
        1296936         3.6.3   
        508b2fd virt: Correct epoll unregistration usage in vmchannels          
        1226911         3.6.3
        68a1b69 virt: Set cloexec flag on channel sockets                       
        1226911         3.6.3
4.17.17 505026d spec: require libvirt to fix hotplugging

So, for the next tag the plan is to

1. branch out ovirt-3.6.2 from tag 4.17.17. This branch is expected to be 
short-lived (basically only for this RC).
2. apply commit 9b29ddd only
3. tag 4.17.18 from branch ovirt-3.6.2

I see we have only two patches in queue for ovirt-3.6

https://gerrit.ovirt.org/#/c/52346/
https://gerrit.ovirt.org/#/c/52348/

Do we need them in this build?

Should we require another 3.6.2 build, backports will be needed ALSO on branch 
ovirt-3.6.2.

Will start implement the plan before lunch if noone objects.

Thanks

-- 
Francesco Romani
RedHat Engineering Virtualization R & D
Phone: 8261328
IRC: fromani
_______________________________________________
Devel mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/devel

Reply via email to