19 Dec
2011
19 Dec
'11
4:31 p.m.
Am 19.12.2011 15:15, schrieb victor martinez:
Because all of these, I am agree with releasing but just, and only
just, if the next actions are done in order to mitigate the bad PR
impact that we will suffer for sure:
1)Adding a message,during 1st stage or before running 2nd stage,
warning the user that a known bug is present which can appear when
copying mshtml file and pointing him to www.reactos.org to find a
solution:
"This release is known to rise a potential bug due to our MM extensive
rewrite. If the installation stucks in mshtml or later, please visit
www.reactos.org, there you will find several ways to solve it. The
ReactOS Team is working to have the MM ready as soon as possible.This
rewrite is needed to ensure the best compatibility and performance.
Sorry for the inconvenience and thanks for your patience. "(or similar)
2)Adding an "Are you suffering the MSHTML bug?" banner in the
frontpage which redirects to a Wiki page explaining the ways to
circumvent the issue and politely asking for Debug Logs.
Sounds good to me.
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.
Instead we could put a note on the frontpage that we are planning to
release soon, but one annoying bug keeps us from doing so.
For everyone who can't wait, we might link a recent build with the
appropriate notes about the mshtml bug.
And regarding the Mm "rewrite": I have doubts it will be done anytime
soon. So fixing the old code should be worth it.
Just my 2 cents,
Timo