[vbox-dev] No Good v4.1.x release to date. Please make more community BETAs
phalbert at cox.net
Sun Oct 9 13:15:09 PDT 2011
I agree with Frank. I have been building against SVN for a long time
and have on occasion found some things that just didn't seem right.
These were reported and fixed. Of course since V 4.*? I can't compile on
Windows but from what I understand this *might be taken care of with V
4.2.* and in which case I will again start testing Win builds again.
IMO it just makes sense to test against SVN instead of beta builds
because it does not cost the DEVs precious time to make ready for a full
On 10/09/2011 02:55 PM, Frank Mehnert wrote:
> On Sunday 09 October 2011 11:52:21 Alexey Eromenko wrote:
>> Since the v4.1.0 release there were no good v4.1.x to date.
>> v4.1.0 - stable and works for me, but lacks linked clones - lacks a
>> killer feature, that should be here.
>> v4.1.2 - has broken GuestControl (in GA) - critical bug.
>> v4.1.4 - has broken PS/2 mouse - critical bug (+broken RHEL4 GA).
>> So far - no good v4.1.x release in the end.
>> Please take care about regressions, and if needed start another community
>> BETA. As a one-time measure please at least do 4.1.6 public BETA, so I can
>> ensure nothing got broken since v4.1.0 days.
> I don't agree. I think the 4.1.4 release is a quite usable release
> and it is IMO better than the last stable release of the 4.0 branch
> There is always a probability for regressions, otherwise it wouldn't
> be possible to implement enhancements and to fix bugs. The regression
> with the RHEL4 kernel is annoying but this bug applies only to a
> specific kernel. And I've just tested mouse grabbing with mouse
> integration disabled -- this works fine here with a Linux host and
> a Linux guest. Maybe this is a problem of the Windows version.
> In general it's a very unbalanced view when concluding from these
> bugs which might be very annoying for you but don't affect many other
> users to a buggy release.
> We will do Betas if possible but building a Beta requires additional
> time and we cannot request Beta tests for every new release. There
> is always a risk for regressions and there will be always a risk. We
> try to keep the risk low but we cannot prevent every regression. We
> just don't have enough resources.
> Kind regards,
> vbox-dev mailing list
> vbox-dev at virtualbox.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the vbox-dev