As of right now, it looks like I'll be pushing the May release next weekend (which is when I plan on making the proposal). But a lot can change until Thursday.
Like I said, I plan on pushing each new release (assuming only bug fixes & cleanups) until the freeze.
For the first new release, I plan on removing some redundant manpages (I know of 3 that need to be removed: vmmemctl, vmxnet3 (both now in the kernel itself), and vmware-toolbox (removed from the package, the CLI version is still there). I think vmware-user should be renamed vmtoolsd, I need someone to confirm this. I will file a bug on this (ETA: Mid July), just so we know/confirm what needs to be removed/updated, in regards to the manpages, before I push the July release (?), in time for Alpha 3.
If there is more than just bug fixes and cleanups in the June/July release, I'll just push a second revision (to the May release), containing the changes to the manpages.
As of right now, it looks like I'll be pushing the May release next weekend (which is when I plan on making the proposal). But a lot can change until Thursday.
Like I said, I plan on pushing each new release (assuming only bug fixes & cleanups) until the freeze.
For the first new release, I plan on removing some redundant manpages (I know of 3 that need to be removed: vmmemctl, vmxnet3 (both now in the kernel itself), and vmware-toolbox (removed from the package, the CLI version is still there). I think vmware-user should be renamed vmtoolsd, I need someone to confirm this. I will file a bug on this (ETA: Mid July), just so we know/confirm what needs to be removed/updated, in regards to the manpages, before I push the July release (?), in time for Alpha 3.
If there is more than just bug fixes and cleanups in the June/July release, I'll just push a second revision (to the May release), containing the changes to the manpages.