On 16.05.2011 16:53, Alexey Eromenko wrote:
It's probably better if you do this with one of the latest BETA before
a release but then we usually run out of time and also don't get in a
good enough state before the release.
Yes, I agree on this one. So for v4.1 cycle, please try to join in
middle of BETA cycle, and once your team finds enough bugs, it will
simply delay VBox release by another week. Final release data is
flexible according to bugs found.
That's not even close to reality. It might seem so for the casual
viewer, but sometimes we have hard deadlines. Generally we try to be as
flexible as possible (which is probably why the wrong impression came
up), finish the main work long before the deadline and release when
everyone is happy, but that's not guaranteed. In such a case FreeBSD
issues will be simply ignored. Sorry, but that's life.
This way you hit less platform neutral bugs, but you stabilize VBox anyway.
Both 3.2 and 4.0 had big amounts of changes all over the place,
including the virtualization core. This greatly increased the risk of
instabilities on certain configs/setups. In the future we don't expect
the need of such big changes "deep down", and thus everything should go
smoothly.
Klaus
_______________________________________________
vbox-dev mailing list
[email protected]
http://vbox.innotek.de/mailman/listinfo/vbox-dev
