Nate, The other distributions are fine with using stable releases recommended by us as they see it as the least risky options, especially since these are versions that we intend to support. RHEL and Fedora actually have policy against using out of tree drivers, so their requirement was to compile open-vm-tools without kernel drivers and for kernel drivers to come from mainline kernel. Same with Suse.
I understand you might want to follow bleeding edge kernels more closely, but I do not think that it is good idea to package such efforts for general consumption and include them in main images installed by everyone. Monthly releases were really just development snapshots. At a given time we'd take top of the internal tree and release it. It could be fine and it could be broken and could eat your filesystem - we would not know because monthly snapshots do not go through full QA cycle. Regarding network drivers - e1000 is the default network device for new VMs an has been for a few years now; you can find pcnet32/vmxnet in very old VMs that are unlikely to get upgraded to newer releases (they'd be using 2.2 kernels I think). Thanks, Dmitry -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1269985 Title: Revert package back to Devel release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1269985/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
