emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
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: Sun, 16 Aug 2015 01:30:20 +0200	[thread overview]
Message-ID: <878u9cjfjn.fsf@free.fr> (raw)
In-Reply-To: <871tf4pbzr.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Sat, 15 Aug 2015 21:50:32 +0200")

Hi Nicolas,

Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:

>> No.  You asked weather it was fine to require Emacs 24.4 in your
>> original message, then people pointed out that Emacs 24.3 was still
>> widely used, then you said it was fine to require Emacs 24.3, just
>> Emacs 24.4 was "icing on the cake".
>
> That's correct, excepted that you were the first to ask "why 24.4 and
> not 24.3"? So I assumed it was between 24.3 and 24.4.

OK, I understand.  I was just curious about why 24.4 and not 24.3,
since 24.4 does not add that much from a developer's point of view.

>> This is not a light decision, as we cannot move back, and I don't
>> see the need for rushing here.
>
> There is no rushing, really. Emacs 24 was released in 2012, and lexical
> binding is a huge step forward for developers. There is some serious
> work involved to make the jump (along with cl-lib switch), so the sooner
> we can start, the better.

I don't mean the rushing in general, I meaning the rushing between
the feedback you asked for and the move to commit things that assume
the answer has been given.

RMS replied to the question on emacs-devel:

  http://article.gmane.org/gmane.emacs.devel/188810

He suggests to continue supporting Emacs 23.

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+.

Maybe we will end up distributing Org 8.3+ for Emacs 23.1 and
Org 9+ for Emacs 24.3+ -- I don't know.

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+.

Thanks,

-- 
 Bastien

  reply	other threads:[~2015-08-15 23:30 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 [this message]
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
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=878u9cjfjn.fsf@free.fr \
    --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).