From: Robert Horn <rjhorn@alum.mit.edu>
To: Bastien Guerry <bzg@gnu.org>
Cc: emacs-orgmode@gnu.org, Phillip Lord <phillip.lord@russet.org.uk>
Subject: Re: org mode moves to GNU emacs core
Date: Mon, 03 Jul 2017 11:23:35 -0400 [thread overview]
Message-ID: <m360f9lf2g.fsf@alum.mit.edu> (raw)
In-Reply-To: <8760f9ae3g.fsf@bzg.fr>
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
next prev parent reply other threads:[~2017-07-03 15:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-29 8:02 org mode moves to GNU emacs core Uwe Brauer
2017-06-29 8:50 ` Rasmus
2017-06-29 9:18 ` Uwe Brauer
2017-07-03 7:28 ` Bastien
2017-07-03 8:33 ` Uwe Brauer
2017-07-03 12:52 ` qTim Cross
2017-07-03 14:21 ` Uwe Brauer
2017-07-03 22:13 ` Tim Cross
[not found] ` <WM!dafdc952e01c9db7d6439bb691272a1ba664e1bae5ab4554e86ed6b7dfea8661d8bbaf476f3ba9dbb09c0c663c84ecc2!@mailhub-mx5.ncl.ac.uk>
2017-07-04 10:45 ` Phillip Lord
[not found] ` <WM!be0b82133cf58eecb5726e88694e8427b36d27c5719f4dbc8d7da9ca2db24765a0806a2a785dcaaf4a6d56d6bd773dc0!@mailhub-mx1.ncl.ac.uk>
2017-07-04 10:36 ` Phillip Lord
[not found] ` <f53ab9c6e9a440bbb5d939a425a97b62@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-07-03 8:52 ` Eric S Fraga
2017-07-03 9:20 ` Alan Schmitt
[not found] ` <WM!87da95345c53f08eaef15c5b7433fda36bb968c366f5815f7f948ed74d91e1259bbc88820ebbf91e3556ee6a4a3e9852!@mailhub-mx5.ncl.ac.uk>
2017-07-03 12:10 ` Phillip Lord
2017-07-03 12:40 ` Bastien Guerry
2017-07-03 15:23 ` Robert Horn [this message]
2017-07-04 8:01 ` Bastien Guerry
[not found] ` <WM!e5e8b591af401b295776634cbabb0d1b446d7bb568c1f8abadd4637a576ff78bf92ed6ccedeed082b016a3f6c9ad6c12!@mailhub-mx3.ncl.ac.uk>
2017-07-04 9:59 ` Phillip Lord
[not found] ` <6d3b27a9e0b245a49cffa029d13bbdb9@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-07-03 13:12 ` Eric S Fraga
2017-07-03 13:30 ` Adonay Felipe Nogueira
2017-07-03 16:52 ` Adonay Felipe Nogueira
2017-07-03 17:58 ` Nick Dokos
2017-07-03 19:38 ` Adonay Felipe Nogueira
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m360f9lf2g.fsf@alum.mit.edu \
--to=rjhorn@alum.mit.edu \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=phillip.lord@russet.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).