all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Juanma Barranquero <lektu@terra.es>
Subject: 21.2.90 pretest, 21.3, 21.4...
Date: Mon, 04 Nov 2002 17:16:24 +0100	[thread overview]
Message-ID: <20021104170119.BAB6.LEKTU@terra.es> (raw)


21.1 was released on 2001-10-20, more than a year ago.

21.2 was released on 2002-03-16, almost eight months ago.

We're just on the second pretest of 21.3. I think it's fair to assume
it'll be still a few months (at least two or three) before 21.3 hits the
streets.  Even if we feature-freeze 21.4-to-be at this moment and start
pretesting it like mad, it'll be almost two years since the last
feature-packed release was introduced to the public.  22.1 with Unicode
will be much further yet along the way.

OK, I know that:
 - we don't *have* to be faster than that
 - we prefer quality releases 
 - people really interested in features vs. stability can access the CVS

Still, I wonder if we should try to pack less punch in each release, and
release a bit faster than we're doing today.  I fear that this (totally
apparent, but public perception counts) stagnation can lead people to
other editors, or (worse, although more improbably) more Emacs branching.

Also, it's tough trying to evangelize people when I know that some
much-appreciated features are just in the HEAD and won't see the light
in a year or two...

Of course, I don't know what we should do, other than attracting more
people to Emacs development. Perhaps a tentative schedule like the one
in GCC would be a first step, but I'm not sure.

Or perhaps the problem is only on my mind; in that case, sorry for
taking your time.


                                                           /L/e/k/t/u

             reply	other threads:[~2002-11-04 16:16 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-04 16:16 Juanma Barranquero [this message]
2002-11-04 18:31 ` 21.2.90 pretest, 21.3, 21.4 Stefan Monnier
2002-11-05  6:05   ` Eli Zaretskii
2002-11-05  7:02     ` Karl Eichwalder
2002-11-05  8:02       ` Juanma Barranquero
2002-11-05 18:40       ` Eli Zaretskii
2002-11-05 20:44         ` Karl Eichwalder
2002-11-06  6:29           ` Eli Zaretskii
2002-11-06  6:58             ` Karl Eichwalder
2002-11-06 14:18               ` Eli Zaretskii
2002-11-08 10:32                 ` Kai Großjohann
2002-11-07 15:07               ` Richard Stallman
2002-11-05  8:02     ` Juanma Barranquero
2002-11-05 18:56       ` Eli Zaretskii
2002-11-05 12:02     ` Kai Großjohann
2002-11-05 19:00       ` Eli Zaretskii
2002-11-05 20:50         ` Stefan Monnier
2002-11-06  6:33           ` Eli Zaretskii
2002-11-06 12:40             ` Kim F. Storm
2002-11-06 12:55               ` Juanma Barranquero
2002-11-06 14:25               ` Eli Zaretskii
2002-11-06 14:49                 ` Juanma Barranquero
2002-11-06 14:51                 ` Miles Bader
2002-11-07 22:02                 ` Francesco Potorti`
2002-11-07  8:08               ` (no subject) Kenichi Handa
2002-11-08 12:06                 ` Richard Stallman
2002-11-07 22:00               ` 21.2.90 pretest, 21.3, 21.4 Francesco Potorti`
2002-11-09 11:54                 ` Richard Stallman
2002-11-06  7:28         ` Kai Großjohann
2002-11-06 14:19           ` Eli Zaretskii
2002-11-06  7:49         ` Juanma Barranquero
2002-11-05 18:39     ` Stefan Monnier
2002-11-05 19:17       ` Eli Zaretskii
2002-11-05 20:37         ` Stefan Monnier
2002-11-06  6:00           ` Eli Zaretskii
2002-11-05  5:58 ` Eli Zaretskii
2002-11-05  7:56   ` Juanma Barranquero
2002-11-05 18:54     ` Eli Zaretskii
2002-11-05 20:40       ` Juanma Barranquero
2002-11-06  6:13         ` Eli Zaretskii
2002-11-06  4:49 ` Richard Stallman
2002-11-06  8:25   ` Juanma Barranquero
  -- strict thread matches above, loose matches on Subject: below --
2002-11-06 15:58 jasonr

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=20021104170119.BAB6.LEKTU@terra.es \
    --to=lektu@terra.es \
    /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.