From: Richard Lawrence <richard.lawrence@berkeley.edu>
To: Bastien <bzg@gnu.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Org release 8.2.5g (minor release from maint)
Date: Thu, 13 Mar 2014 09:28:45 -0700 [thread overview]
Message-ID: <87r466ysea.fsf@berkeley.edu> (raw)
In-Reply-To: <87vbvijghj.fsf@bzg.ath.cx>
Hi Bastien,
Bastien <bzg@gnu.org> writes:
> Any reason why Debian developers are not using 24.3 as the stable
> version of Emacs? It has been out for now one year.
Well, the way that the Debian stable release works is that they ship the
latest stable version of a package which is available at the time of
their pre-release "freeze". After the freeze, packages only receive
updates for critical bugs and security fixes for the lifetime of the
release.
The current release (Debian Wheezy) was frozen on 2012-06-30 and
released 2013-05-04. I think Emacs 24 probably just barely missed the
Wheezy release, as 24.1 was released 2012-06-10. My guess is that the
Debian maintainers either didn't consider 24.1 stable enough yet for
Wheezy, or they just weren't sure and didn't want to take the chance.
The next release (Jessie) is not yet frozen, and some post-24 Emacs will
certainly be included when it is.
Anyway, I don't think Org should be beholden to distributions' release
cycles in general. Users like me who are happy with an older Emacs but
want a newer Org are probably a very small minority (but speak up if
you're out there!). And for these users, it is probably only a minor
inconvenience to have to install cl-lib or a newer Emacs. That is at
least true in my case. If introducing a dependency on cl-lib right now
will be the best thing for Org, I have no real objections; if it can be
put off for a while without significant cost, that would be great, but
it isn't necessary.
Best,
Richard
next prev parent reply other threads:[~2014-03-13 16:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-21 13:50 Org release 8.2.5g (minor release from maint) Bastien
2014-01-21 19:16 ` Achim Gratz
2014-01-21 19:25 ` Bastien
2014-01-21 19:30 ` Bastien
2014-01-21 19:35 ` Achim Gratz
2014-01-21 23:39 ` Bastien
2014-01-22 7:52 ` Achim Gratz
2014-01-25 7:58 ` Achim Gratz
2014-02-26 19:25 ` Achim Gratz
2014-02-26 23:23 ` Eric Schulte
2014-03-01 8:06 ` Bastien
2014-03-01 9:10 ` Achim Gratz
2014-03-01 12:53 ` Nick Dokos
2014-03-03 3:03 ` Eric Schulte
2014-03-05 1:56 ` Eric Abrahamsen
2014-03-05 3:20 ` Nick Dokos
2014-03-06 17:00 ` Eric Schulte
2014-03-07 7:26 ` Bastien
2014-03-07 16:05 ` Richard Lawrence
2014-03-07 21:09 ` Eric Schulte
2014-03-08 4:05 ` Richard Lawrence
2014-03-13 14:55 ` Bastien
2014-03-13 16:28 ` Richard Lawrence [this message]
2014-03-21 8:08 ` Bastien
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=87r466ysea.fsf@berkeley.edu \
--to=richard.lawrence@berkeley.edu \
--cc=bzg@gnu.org \
--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).