unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Eli Zaretskii" <eliz@is.elta.co.il>
Cc: simon.marshall@misys.com, emacs-devel@gnu.org
Subject: Re: emacs 21.2
Date: Sat, 23 Mar 2002 10:59:44 +0200	[thread overview]
Message-ID: <9791-Sat23Mar2002105944+0200-eliz@is.elta.co.il> (raw)
In-Reply-To: <87g02si2fi.fsf@tc-1-100.kawasaki.gol.ne.jp> (message from Miles Bader on 23 Mar 2002 08:54:25 +0900)

> From: Miles Bader <miles@gnu.org>
> Date: 23 Mar 2002 08:54:25 +0900
> 
> On the other hand, a traditional pretest is too late for many kinds of
> changes, so I wonder if it would be a good idea to officialy have two
> stages in the pretest:
> 
>    (stage 1)  Did everything important get fixed?
>    (stage 2)  [a more normal `no big changes' pretest]

Alternatively, we could announce a planned beginning of a pretest
some time, like a month, in advance, and ask the pretesters to try
the CVS code.  (A snapshot of the CVS could be prepared at that time,
if accessing the CVS is not good enough.)

In general, development on both the trunk and branch is a pain, and
also prone to errors, so it should be avoided, I think.  It's better
to have a feature freeze when the branch is cut, I think.

_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel


  reply	other threads:[~2002-03-23  8:59 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-22 12:43 emacs 21.2 Marshall, Simon
2002-03-22 14:21 ` Eli Zaretskii
2002-03-22 15:20   ` Marshall, Simon
2002-03-22 16:36     ` Juanma Barranquero
2002-03-22 17:45     ` Eli Zaretskii
2002-03-22 19:38     ` Jason Rumney
2002-03-22 23:54     ` Miles Bader
2002-03-23  8:59       ` Eli Zaretskii [this message]
2002-03-23 16:15     ` Richard Stallman
2002-03-23  9:03   ` Per Abrahamsen
2002-03-23 10:12     ` Eli Zaretskii
2002-03-24 15:51     ` Richard Stallman
2002-03-24 18:04       ` Eli Zaretskii
2002-03-25 12:02         ` Richard Stallman
2002-03-25 19:45           ` Eli Zaretskii
2002-03-26 10:14             ` Werner LEMBERG
2002-03-28  4:55               ` Richard Stallman
2002-03-28  9:37                 ` Eli Zaretskii
2002-03-29 17:15                   ` Florian Weimer
2002-03-29 17:32                     ` Eli Zaretskii
2002-03-29 17:47                       ` Florian Weimer
2002-03-22 16:52 ` Stefan Monnier
  -- strict thread matches above, loose matches on Subject: below --
2002-03-22 17:34 Marshall, Simon
2002-03-22 18:47 ` Eli Zaretskii
2002-03-22 17:05 Marshall, Simon
2002-03-22  9:40 Marshall, Simon
2002-03-22 11:44 ` Eli Zaretskii
2002-03-23 16:13 ` Richard Stallman

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=9791-Sat23Mar2002105944+0200-eliz@is.elta.co.il \
    --to=eliz@is.elta.co.il \
    --cc=emacs-devel@gnu.org \
    --cc=simon.marshall@misys.com \
    /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).