|
From: | Jason Rumney |
Subject: | Re: Next release |
Date: | Sun, 04 May 2008 15:34:28 +0100 |
User-agent: | Thunderbird 2.0.0.14 (Windows/20080421) |
Eli Zaretskii wrote:
You seem to assert that when faced with changes which could potentially break other platforms, there's only two possible alternatives: either live with the breakage or don't commit the code at all. But in fact, there's a 3rd alternative: learn enough about those other platforms to make the code right on them as well. There's even a 4th alternative: make the new code be conditionally compiled only on platforms you understand and can test. All of those are IMO better than breakage.
I think the lack of detailed documentation for some of the large code changes that have been developed on a branch makes things difficult for those who need to port the changes to other platforms. It can be quite daunting to be faced with such code breakage coming from three different sources (multi-tty, unicode and font-backend) at around the same time, when you have limited time to spend on getting things working again, meanwhile complaints from users flood in.
[Prev in Thread] | Current Thread | [Next in Thread] |