From: Chong Yidong <cyd@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: Update on the Emacs release schedule?
Date: Sat, 07 Jan 2012 15:10:38 +0800 [thread overview]
Message-ID: <87vcookmxd.fsf@gnu.org> (raw)
In-Reply-To: <m34nw89l0p.fsf@stories.gnus.org> (Lars Magne Ingebrigtsen's message of "Sat, 07 Jan 2012 05:47:18 +0100")
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Are we getting much closer to the Emacs 24.1 release date? I think that
> Emacs is looking pretty solid, and I'm kinda wondering what we're
> waiting for. :-)
We are getting closer indeed, but the documentation updates are not
done. We're due for another pretest, but there are a couple more
off-list issues I'd like to wrap up first.
As for the code, there are still a number of issues that need more
attention, most prominently the mysterious memory leak(s) that may or
may not involve Gnus and/or GnuTLS and/or Mac OS X.
By the by, could someone please take a look at this Viper bug?
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=9146
next prev parent reply other threads:[~2012-01-07 7:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-07 4:47 Update on the Emacs release schedule? Lars Magne Ingebrigtsen
2012-01-07 7:10 ` Chong Yidong [this message]
2012-01-07 11:02 ` Carsten Mattner
2012-01-07 13:45 ` Ted Zlatanov
2012-01-07 17:02 ` Carsten Mattner
2012-01-07 18:11 ` Stefan Monnier
2012-01-07 18:32 ` Carsten Mattner
2012-01-07 20:13 ` Jan Djärv
2012-01-08 13:54 ` Stefan Monnier
2012-01-07 13:44 ` fixing memory leaks before the pretest (was: Update on the Emacs release schedule?) Ted Zlatanov
2012-01-07 15:49 ` fixing memory leaks before the pretest Chong Yidong
2012-01-10 0:59 ` Ted Zlatanov
2012-01-07 16:57 ` fixing memory leaks before the pretest (was: Update on the Emacs release schedule?) Carsten Mattner
2012-01-08 2:39 ` YAMAMOTO Mitsuharu
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vcookmxd.fsf@gnu.org \
--to=cyd@gnu.org \
--cc=emacs-devel@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.