unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org, mh-e-devel@lists.sourceforge.net
Subject: Re: Continued development during release process
Date: Sat, 22 Apr 2006 18:32:30 -0400	[thread overview]
Message-ID: <E1FXQeU-0001sC-Df@fencepost.gnu.org> (raw)
In-Reply-To: <2167.1145655433@olgas.newt.com> (message from Bill Wohler on Fri, 21 Apr 2006 14:37:13 -0700)

    Second, once you add a pretest tag, will you make subsequent tags based
    upon that tag, or will you simply tag the trunk?

I did not understand your question at first because of some CVS jargon
I did not know, but now I understand the issue.

We don't have any rule about this.  I decide what to do,
though I don't implement it in CVS.

I want to keep people's attention focused on the release until the
release actually comes out.  So I will not relegate the coming release
22 to a branch when pretesting starts.

If we reach a late stage of pretesting where there are few bugs, and
mostly waiting for a few specific people to fix them, maybe I will
move 22 to a branch then.


-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

  parent reply	other threads:[~2006-04-22 22:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-21 21:37 Continued development during release process Bill Wohler
2006-04-22 10:35 ` Eli Zaretskii
2006-04-23 16:01   ` Bill Wohler
2006-04-23 20:59     ` Kim F. Storm
2006-04-24  2:38       ` Bill Wohler
2006-04-22 22:32 ` Richard Stallman [this message]
2006-04-23 14:10   ` Stefan Monnier

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=E1FXQeU-0001sC-Df@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=mh-e-devel@lists.sourceforge.net \
    /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).