unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Query re `format-mode-line'
Date: Fri, 08 Sep 2006 18:36:28 +0200	[thread overview]
Message-ID: <85mz9al3hv.fsf@lola.goethe.zz> (raw)
In-Reply-To: <EIENLHALHGIMHGDOLMIMGEDFCLAA.drew.adams@oracle.com> (Drew Adams's message of "Fri\, 8 Sep 2006 08\:58\:00 -0700")

"Drew Adams" <drew.adams@oracle.com> writes:

>         Do only bug fixes go into minor version updates such as
>         21.4?  Or put another way, have there been no new functions
>         introduced into the Emacs that most people use since 2001?
>
>     Yes.
>
> Does this mean that adding new features "after the release" really
> means they won't be available until the next major release (circa
> 2048)? We and our great grandchildren will miss them. ;-)

Emacs 23 is the unicode2 branch.  It is being maintained in parallel
at the moment and kept in reasonable shape, and some stuff has been
merged into it that is not in Emacs 22 if I remember correctly.  When
Emacs 22 is out and reasonably debugged, so that we won't need more
22.x releases, the unicode branch will get merged to HEAD.  Then this
will get merged into the multi-tty branch, and when this seems
successful, the merge of multi-tty will go back into HEAD as well.

Both branches are in reasonable shape AFAIK.  When most of the merges
are through and it is clear whether we will release with multi-tty or
not, adding new features starts making sense again.  Those should,
however, be not too potentially destabilizing (like the lexical-let
branch, I would guess, or Emacs-bidi).

This is the idea of the next release after Emacs 22, and, considering
the state of affairs in the branches, it should not take much more
than half a year.  After all, the manual and code are in a good shape
with our current release, and the Emacs 23 changes are somewhat
localized.

Once unicode2 has become HEAD, there will be sense again in working
seriously on the Bidi branch.  However, it is not clear when that will
be fit for merging.

I don't see what you hope to accomplish by pressing for destabilizing
development right now with new features.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

  reply	other threads:[~2006-09-08 16:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-07 17:40 Query re `format-mode-line' Robert J. Chassell
2006-09-08 11:56 ` Richard Stallman
2006-09-08 15:58   ` Drew Adams
2006-09-08 16:36     ` David Kastrup [this message]
2006-09-08 17:41       ` Drew Adams
2006-09-08 21:52       ` Nick Roberts
2006-09-08 22:01         ` Drew Adams
2006-09-11  2:46           ` Miles Bader
2006-09-11 19:57             ` Richard Stallman
2006-09-08 16:39     ` Eli Zaretskii

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.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=85mz9al3hv.fsf@lola.goethe.zz \
    --to=dak@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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.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).