19 Dec
2011
19 Dec
'11
5:02 p.m.
On Dec 19, 2011, at 11:31 AM, Timo Kreuzer wrote:
Am 19.12.2011 15:15, schrieb victor martinez:
The trouble is that we don't know where the corruption is
taking place in the code.
3)Adding a massive DPRINTing in the MM and friends to find a clue about why MM is going
nuts.
Doesn't sound good to me. Massive DPRINTs just make the system slow and
usually don't give a clue, unless you are actively debugging it. Also our debuglog is
already full of spam.
I'm personally against releasing with this bug. It will affect a huge number of
people who want to test the new release and the first thing they encounter is the
inability to install.
Delaying the release for another month or 2 on the other hand doesn't make thing much
worse than they are now already.
The only problem I have with delaying the release is that we're getting more
and more out of date with Wine and some great patches are waiting on the release. My vote
would be to branch now, run 0.3.14 tests on the branch, then resume trunk development as
if we had just released (Winesyncs, big patches, etc). After the Mm bug is found, we can
either rebranch 0.3.14 if trunk is stable or merge the fix back and release the previous
branch.
And regarding the Mm "rewrite": I have
doubts it will be done anytime soon. So fixing the old code should be worth it.
I agree, and as a result RosMm sucks considerably less now ;)
Regards,
Cameron