unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juanma Barranquero <lektu@terra.es>
Cc: Eli Zaretskii <eliz@is.elta.co.il>,
	Stefan Monnier <monnier+gnu/emacs@rum.cs.yale.edu>,
	emacs-devel@gnu.org
Subject: Re: 21.2.90 pretest, 21.3, 21.4...
Date: Wed, 06 Nov 2002 13:55:02 +0100	[thread overview]
Message-ID: <20021106133553.66AB.LEKTU@terra.es> (raw)
In-Reply-To: <5xbs52oor1.fsf@kfs2.cua.dk>

On 06 Nov 2002 13:40:18 +0100, storm@cua.dk (Kim F. Storm) wrote:

> IMO, a feature freeze on the trunk at the current state would be OK!

I agree.

> So I suggest that we announce a date (e.g. Dec 1st) for a trunk
> feature freeze and make the first pretest for 21.4 soon thereafter,
> with the goal of releasing 21.4 no later than Mar 1st, 2003!

I think those are reasonable goals. Dec 1st for the freeze leaves time
enough for those who really *want* to include something in the 21.4 (at
least, if that "something" is not big, and if it is, it would be better
to wait for 21.5 anyway, IMO). That's four months of pretesting at the
bare minimum.  And we can always slip past the deadline... :)

> In my experience, the trunk has been very stable for a very long time
> [with a few hickups of course], so after the first few pretests, I
> would assume that the software would be stable enough for a release,
> or at least stable enough that we could make a 21_4 release branch for
> ironing out the final issues with the 21.4 release and remove the
> feature freeze on the trunk before Mar 1st (or whenever 21.4 will
> actually be ready).

Yes. I agree wrt stability of the trunk. I use 21.3.50 daily in my
production environment.  I don't remember the last time I had a crash;
many months ago. Several times I wasn't able to compile or bootstrap,
but if it compiles, it is rock-solid.

> Are anyone of you aware of any significant stability (or redisplay)
> related bugs that we need to fix before 21.4 ?

I know of two problems. At least one of them is Windows-specific, but I
don't know how to fix it: if you use w32-select-font and get an
*-iso10646-1 font, pasting it into the Registry
(HKLM\Software\GNU\Emacs\Font) garbles Emacs display. It looks like
Emacs isn't aware it's using an Unicode font. That happens both in the
RC and HEAD branches.

The other, related to some changes by Richard a few months ago, is that
the scroll line-by-line doesn't work when you're displaying the
ruler (or any other thing that makes Emacs show partially-visible lines).
In that case scroll always recenter the cursor irrespective of the value
of `scroll-conservatively'. It's a redisplay bug, but minor. Happens
only on the trunk.

> WDYT ??

FWIW, I think that any reasonable mesure to take the new features out to
the public light is good.


                                                           /L/e/k/t/u

  reply	other threads:[~2002-11-06 12:55 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-04 16:16 21.2.90 pretest, 21.3, 21.4 Juanma Barranquero
2002-11-04 18:31 ` 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 [this message]
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

  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=20021106133553.66AB.LEKTU@terra.es \
    --to=lektu@terra.es \
    --cc=eliz@is.elta.co.il \
    --cc=emacs-devel@gnu.org \
    --cc=monnier+gnu/emacs@rum.cs.yale.edu \
    /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).