From mboxrd@z Thu Jan 1 00:00:00 1970 From: Achim Gratz Subject: Re: [DEV] Bump Emacs requirement to 24.4? Date: Sun, 16 Aug 2015 08:08:15 +0200 Message-ID: <87twrzkbow.fsf@Rainer.invalid> References: <87io8tfrtk.fsf@nicolasgoaziou.fr> <87vbctieu3.fsf@gmx.us> <20150806074217.00177cc9@zotac> <87lhdohmii.fsf@nicolasgoaziou.fr> <87bnekrfgi.fsf@gmx.us> <874mk15862.fsf@gnu.org> <87pp2povpl.fsf@nicolasgoaziou.fr> <87y4hddl2y.fsf@free.fr> <87a8tsq4d9.fsf@nicolasgoaziou.fr> <87zj1sk4uf.fsf@free.fr> <871tf4pbzr.fsf@nicolasgoaziou.fr> <878u9cjfjn.fsf@free.fr> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:48310) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZQr7M-0002Pj-Dt for emacs-orgmode@gnu.org; Sun, 16 Aug 2015 02:08:29 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZQr7J-0006Vk-81 for emacs-orgmode@gnu.org; Sun, 16 Aug 2015 02:08:28 -0400 Received: from plane.gmane.org ([80.91.229.3]:55040) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZQr7J-0006V7-10 for emacs-orgmode@gnu.org; Sun, 16 Aug 2015 02:08:25 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1ZQr7G-0001W2-SW for emacs-orgmode@gnu.org; Sun, 16 Aug 2015 08:08:23 +0200 Received: from p4ff1cd16.dip0.t-ipconnect.de ([79.241.205.22]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 16 Aug 2015 08:08:22 +0200 Received: from Stromeko by p4ff1cd16.dip0.t-ipconnect.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 16 Aug 2015 08:08:22 +0200 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Bastien writes: > So my suggestion still stands: > > - let's keep master in the current compatibility state since the > question you asked still needs to be answer (it's just 10 days > since it was asked). > > - let's use a dedicated branch for commits requiring Emacs 24.3+. I'm with Nicolas on this point: if we end up de-supporting Emacs 23, then the master branch is where that should happen. Since it already has happened and the general consensus seems to be that we should go there eventually, just maybe not right now, I don't see why we suddenly also need to re-define what master is about. > Maybe we will end up distributing Org 8.3+ for Emacs 23.1 and > Org 9+ for Emacs 24.3+ -- I don't know. What the next release from master will be called is not yet decided. But we can and should decide that maint does not de-support Emacs 23 until and only after proper announcement. That might ultimately end up needing a separate maint23 branch for cherry-picking some bug-fixes after the development has swicthed to Emacs24.3+ on maint, although I don't see where the developer resources would come from to keep three branches in flight, especially when apparently some developers don't have Emacs23 at their disposal (actually that is what I have the RaspberryPi for, believe it or not). > Let's take 10-15 days to build a strategy together, with feedbacks > from various sources and information we share. We need this time > to consider the question seriously. Please revert the changes in > master that assume Org needs Emacs 24.3+. There's no need to rush that decision either. I am one of those who still need to run on Emacs23 and I will just switch from master to maint for that. I don't see any pressing bugs or missing features there either, so if I'd need to freeze Emacs23 to some specific point in the history that would quite likely also work. From what happened with Emacs 22, I expect at least another two years before I can generally assume availability of Emacs 24.3+ on all systems. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ DIY Stuff: http://Synth.Stromeko.net/DIY.html