Paul Schmehl wrote:
> Furthermore, it seems the reaction of developers, that he wasn't being
> specific enough are rendered moot by the urls above, which were easily
> accessed by me, someone with little knowledge at all of two of the
> three issues. So, rather than berating Jo for not producing PRs,
> wouldn't it have been more professional to list the relevant PRs (just
> as I have done, which took me less time than the multiple angry
> responses to Jo took the involved developers) and ask him which of
> them gave him the greatest concerns?
I'm sure I'm not the only person besides yourself who's actually done
the searches to see if there are any PRs I may be able to shed light on
for Jo. I also briefly read each PR, and even a brief persual would show:
> That url lists 6 serious problems for bge and 3 non-critical problems,
> some dating to more than two years ago. Two were patched, one is
> suspended and 6 are still open; four of those critical.
Only 3 (2 critical and one patched) of which are specific to 6.3. One
is specific to IPv6 and one only occurring on the second of a dual-card
configuration; we have no reason to believe that either of these relate
to Jo's environment without his providing that kind of detail.
> That url lists 1 serious problem and 3 non-critical problems with
> gmirror, all of which remain open.
Only one of these is specific to 6.3, and it appears very low priority,
> That url refers to locking problems that cause kernel panics using the
> twe driver.
This appears to be a bug in aac, not twe.
> That url refers to a hang that renders a system unusable when using
> the twa driver.
And it was present in 6.2.
Unfortunately the URLs only serve to make the developer's points for
them. None of them gives any indication of what problem Jo may be
referring to that is preventing him from upgrading to 6.3. Remember, he
claims to have multiple servers running 6.2 with no issues, and is only
concerned with upgrades to 6.3. He also stated that the PR's he's
worried about explicitly stated that they could not be reproduced in
6.2, so any bug that existed in 6.2 clearly doesn't qualify. That rules
out all but two bugs, both of which are so specific to a given hardware
setup that it would be impossible to know if they apply in this case or not.