From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: [DEV] Bump Emacs requirement to 24.4?
Date: Sun, 16 Aug 2015 08:08:15 +0200 [thread overview]
Message-ID: <87twrzkbow.fsf@Rainer.invalid> (raw)
In-Reply-To: 878u9cjfjn.fsf@free.fr
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 <whatever version> 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
next prev parent reply other threads:[~2015-08-16 6:08 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 [this message]
2015-08-16 8:13 ` Bastien Guerry
2015-08-16 18:03 ` Achim Gratz
2015-08-18 23:01 ` Bastien
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=87twrzkbow.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=emacs-orgmode@gnu.org \
/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).