all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Are we in feature-freeze?
Date: Sat, 27 Sep 2008 08:25:44 -0400	[thread overview]
Message-ID: <jwvfxnlye73.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <ud4iqkm9c.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 27 Sep 2008 11:48:15 +0300")

> Emacs 23 is in feature-freeze, right?

Yes.

> Or was it lifted?

No.

> (And while at that: what are the current estimations of Emacs 23
> release date or the beginning of its pretest cycle?)

Waiting for the number of open bugs to come down.  I've been overwhelmed
for the last couple months, so I haven't been able to help much on that
front, sadly.  I'm hoping to being the prestest around December/January.

> I see new features being committed to the trunk and plans of extending
> these features being discussed, so I thought I'd ask: is it okay to
> add new features at this time, and if so, which features can be added?

Other than the `daemon' mode, which features have been added recently?
I have no intention to extend the daemon mode before the release.

> For example, I have a working version of getloadavg for MS-Windows,
> which would allow "M-x display-time" to show the load in the mode line
> when Emacs runs on Windows.  Is it okay to commit changes to do
> that now?

I'd prefer to wait for that.


        Stefan




  reply	other threads:[~2008-09-27 12:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-27  8:48 Are we in feature-freeze? Eli Zaretskii
2008-09-27 12:25 ` Stefan Monnier [this message]
2008-09-27 14:51   ` Eli Zaretskii
2008-09-27 19:50   ` Chong Yidong
2008-09-27 23:27   ` Nick Roberts
2008-09-28  3:03     ` Chong Yidong
2008-09-28  3:25       ` Eli Zaretskii
2008-09-28  5:13         ` Chong Yidong
2008-09-28  7:22       ` Nick Roberts

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=jwvfxnlye73.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=eliz@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.