From: Bastien <bzg@gnu.org>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: emacs-orgmode@gnu.org, Rasmus <rasmus@gmx.us>
Subject: Re: [DEV] Bump Emacs requirement to 24.4?
Date: Wed, 19 Aug 2015 01:01:29 +0200 [thread overview]
Message-ID: <87oai4w69i.fsf@gnu.org> (raw)
In-Reply-To: <87y4hddl2y.fsf@free.fr> (Bastien Guerry's message of "Sat, 15 Aug 2015 10:15:01 +0200")
Hi Nicolas and all,
As Achim said, we may have been miscommunicating, especially on
whether it was about requiring Emacs 23+ or 24.3 vs 24.4.
Here is my decision on this issue:
- the Org 8.x series will be Emacs 23+ compatible.
- the Org 9.x series will be Emacs 24.3+ compatible.
Emacs 23 and XEmacs support will be officially dropped as of Org 9.0.
The maint branch continues to be used to work on minor releases, as it
has always been used.
Instead of reverting changes from the master branch (you clearly don't
want to do that, and I don't either), I suggest we create a new branch
called "org-8-master" for Org 8.4+, and continue to use master for Org
9.x+ (i.e. "major major releases").
This is temporary: once the 9.0 version is released, we can simply use
maint and master as before, and delete org-8-master.
The reason for this is that we need to make room for new features in
the 8.x series, so that these new features will be available to the
Emacs 23 users.
If we drop Emacs 23 support as of Org 8.4, we won't be able to add new
features (e.g. new export backends) for Emacs 23.
I recognize having the manpower to watch after those branches might be
an issue, but we can overcome it by calling for careful testing before
major releases.
Let me know what you think,
--
Bastien
next prev parent reply other threads:[~2015-08-18 23:01 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-05 19:39 [DEV] Bump Emacs requirement to 24.4? Nicolas Goaziou
2015-08-05 19:38 ` Kaushal
2015-08-05 21:13 ` Suvayu Ali
2015-08-05 21:51 ` Rasmus
2015-08-06 5:42 ` Robert Klein
2015-08-06 8:03 ` Nicolas Goaziou
2015-08-06 8:23 ` Robert Klein
2015-08-06 8:25 ` Rasmus
2015-08-15 7:21 ` Bastien Guerry
2015-08-15 7:29 ` Nicolas Goaziou
2015-08-15 8:15 ` Bastien Guerry
2015-08-15 8:30 ` Rasmus
2015-08-15 8:37 ` Bastien Guerry
2015-08-15 9:51 ` Nicolas Goaziou
2015-08-15 10:02 ` Rasmus
2015-08-15 12:14 ` Robert Horn
2015-08-15 9:37 ` Nicolas Goaziou
2015-08-15 14:23 ` Bastien Guerry
2015-08-15 19:50 ` Nicolas Goaziou
2015-08-15 23:30 ` Bastien
2015-08-16 6:08 ` Achim Gratz
2015-08-16 8:13 ` Bastien Guerry
2015-08-16 18:03 ` Achim Gratz
2015-08-18 23:01 ` Bastien [this message]
2015-08-19 5:22 ` David Engster
2015-08-19 9:52 ` Bastien
2015-08-19 6:04 ` Suvayu Ali
2015-08-19 9:40 ` Bastien
2015-08-19 10:31 ` Suvayu Ali
2015-08-19 16:11 ` Achim Gratz
2015-08-19 20:07 ` Rasmus
2015-08-20 23:02 ` Bastien
2015-09-16 7:58 ` Rasmus
2015-08-05 22:22 ` Bastien Guerry
2015-08-06 1:07 ` Nicolas Goaziou
2015-08-15 8:45 ` Achim Gratz
2015-08-15 9:28 ` Nicolas Goaziou
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=87oai4w69i.fsf@gnu.org \
--to=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
--cc=rasmus@gmx.us \
/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).