From mboxrd@z Thu Jan 1 00:00:00 1970 From: Robert Horn Subject: Re: org mode moves to GNU emacs core Date: Mon, 03 Jul 2017 11:23:35 -0400 Message-ID: References: <87injf1asi.fsf@mat.ucm.es> <87r2xyvv1q.fsf@gnu.org> <87wp7ppvpz.fsf@russet.org.uk> <8760f9ae3g.fsf@bzg.fr> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:59867) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dS3CQ-0000Ky-A8 for emacs-orgmode@gnu.org; Mon, 03 Jul 2017 11:23:43 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dS3CP-0007LB-FO for emacs-orgmode@gnu.org; Mon, 03 Jul 2017 11:23:42 -0400 In-reply-to: <8760f9ae3g.fsf@bzg.fr> 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" To: Bastien Guerry Cc: emacs-orgmode@gnu.org, Phillip Lord Bastien Guerry writes: > Hi Philip, > > phillip.lord@russet.org.uk (Phillip Lord) writes: > >> I presume you do see this as an advantage? The issue is, surely, >> that it's too much of a PITA for the advantage that you gain? > > Well, it's not really about PITA-or-not-PITA, it's just that I want > org-mode to be the default mode for some files in Emacs, and having > org-mode in Emacs' core is the most simple way to go for this. > I just did a quick check of my git repositories for org-mode and emacs. There is a significant difference in release cycle policies, and this will affect users. Emacs makes a release about once every 9 months, usually a point release. Major feature releases are less frequent. Org-mode makes a release about once per month, also usually a point release. I think that switching to the emacs cycle would be perceived as making org-mode far less responsive to problem reports and feature improvements. There are ways that the git repositories and release policies can be organized to enable more rapid response to minor bugs and small features while still integrating into core emacs. I think that you should figure out a mutually acceptable means of maintaining the present rapid responsiveness. With a suitable structuring of make files, etc., you can probably also deal with the performance issues associated with building updated versions. The emacs maintainers would have to agree. It does call for a little more setup work, and probably a semi-permanent branch structure in git to allow for org updates, while gaining most of what you want. It would also mean that those who want to stay on the leading edge of org-mode would need to maintain git synchronization with emacs rather than org-mode. With good explanation and documentation that shouldn't be too much of a problem. I do it already on an ad-hoc basis because I found elpa to be too problematic. R Horn