From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Jason Rumney Newsgroups: gmane.emacs.devel Subject: Re: Next release Date: Sun, 04 May 2008 15:34:28 +0100 Message-ID: <481DC974.7080202@gnu.org> References: <18457.37369.262079.668907@kahikatea.snap.net.nz> <5jr6clncn8.fsf@fencepost.gnu.org> <87od7p22dw.fsf@stupidchicken.com> <200805021331.m42DVYVw016584@sallyv1.ics.uci.edu> <200805021610.m42GAhkE001271@sallyv1.ics.uci.edu> <200805040056.m440u3eS022727@sallyv1.ics.uci.edu> <200805040206.m4426oct013714@sallyv1.ics.uci.edu> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1209911721 12619 80.91.229.12 (4 May 2008 14:35:21 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 4 May 2008 14:35:21 +0000 (UTC) Cc: Dan Nicolaescu , emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun May 04 16:35:57 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1JsfJi-0006Of-Qi for ged-emacs-devel@m.gmane.org; Sun, 04 May 2008 16:35:55 +0200 Original-Received: from localhost ([127.0.0.1]:57906 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JsfJ0-0000fp-Vs for ged-emacs-devel@m.gmane.org; Sun, 04 May 2008 10:35:11 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JsfIX-00009j-Vb for emacs-devel@gnu.org; Sun, 04 May 2008 10:34:42 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JsfIT-0008VN-4E for emacs-devel@gnu.org; Sun, 04 May 2008 10:34:41 -0400 Original-Received: from [199.232.76.173] (port=44614 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JsfIS-0008Uz-R9 for emacs-devel@gnu.org; Sun, 04 May 2008 10:34:36 -0400 Original-Received: from mk-outboundfilter-4.mail.uk.tiscali.com ([212.74.114.32]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JsfIO-0003sw-2Q; Sun, 04 May 2008 10:34:32 -0400 Original-X-Trace: 74129408/mk-outboundfilter-2.mail.uk.tiscali.com/F2S/$ACCEPTED/freedom2Surf-customers/83.67.23.108 X-SBRS: None X-RemoteIP: 83.67.23.108 X-IP-MAIL-FROM: jasonr@gnu.org X-IP-BHB: Once X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: As8EAL5lHUhTQxds/2dsb2JhbACBU6gQ X-IP-Direction: IN Original-Received: from i-83-67-23-108.freedom2surf.net (HELO wanchan.jasonrumney.net) ([83.67.23.108]) by smtp.f2s.tiscali.co.uk with ESMTP; 04 May 2008 15:34:30 +0100 Original-Received: from [192.168.249.27] (chiko.jasonrumney.net [192.168.249.27]) by wanchan.jasonrumney.net (Postfix) with ESMTP id 8FF3918B3; Sun, 4 May 2008 15:34:30 +0100 (BST) User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) In-Reply-To: X-Enigmail-Version: 0.95.6 OpenPGP: id=8086879D X-detected-kernel: by monty-python.gnu.org: Genre and OS details not recognized. X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:96438 Archived-At: 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.