unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu>
Cc: Juanma Barranquero <jmbarranquero@laley.wke.es>
Subject: Re: Major update just committed
Date: Sat, 31 May 2003 16:33:37 -0400	[thread overview]
Message-ID: <200305312033.h4VKXbcJ000827@rum.cs.yale.edu> (raw)
In-Reply-To: E19MCOi-0007Yc-PQ@fencepost.gnu.org

>     Glad to hear, if that means we *will* branch for 21.5 after Gnus and
>     CC-mode are here.
> 
> I don't think we should make a branch for the next non-bug-fix
> release.  We should think of what will be the next non-bug-fix release
> as the main focus of work, so it should be in the trunk.  It will need
> a considerable amount of work to become reliable, I expect.  Some
> smaller features can still be installed during that time.
> 
> Rather, people should start putting major changes into other branches.

If we have another branch (other than unicode) for major changes,
then we will not really focus on the trunk, methinks.

So I think we should do like we did for 21.1 and like most projects
do AFAIK, which is to say "freeze", spend some months debugging
and then (and only then) make a new branch (which is the release branch).

During the debugging phase people should just refrain from any "major work"
which would distract them from debugging.  When this "refraining" because
too difficult, it's a sign that there isn't enough debugging to do any more,
so it's a good time to branch.

As you said, it will probably take time to debug this beast, so we
should start the freeze as soon as possible.


	Stefan

  reply	other threads:[~2003-05-31 20:33 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-25  0:48 Major update just committed Kim F. Storm
2003-05-25  1:26 ` Juanma Barranquero
2003-05-25  8:23   ` David Ponce
2003-05-26  3:47 ` Miles Bader
2003-05-28  0:18   ` Kim F. Storm
2003-05-27 13:28 ` Kenichi Handa
2003-05-28  0:16   ` Kim F. Storm
2003-05-27 22:39     ` Stefan Monnier
2003-05-28  3:53       ` Eli Zaretskii
2003-05-28 23:58         ` Richard Stallman
2003-05-29  3:46           ` Eli Zaretskii
2003-05-29 13:45             ` Stefan Monnier
2003-05-29 17:15             ` Juanma Barranquero
2003-05-29 17:24               ` Stefan Monnier
2003-05-30  0:55                 ` Kim F. Storm
2003-05-30  0:48               ` Richard Stallman
2003-05-30  7:23                 ` Juanma Barranquero
2003-05-31 19:52                   ` Richard Stallman
2003-05-31 20:33                     ` Stefan Monnier [this message]
2003-06-01 12:58                       ` Jason Rumney
2003-06-01 15:51                       ` Eli Zaretskii
2003-06-04  8:54                       ` Richard Stallman
2003-06-01 15:24                     ` Juanma Barranquero
2003-06-01 20:11                       ` Jason Rumney
2003-06-01 15:49               ` Eli Zaretskii
2003-06-01 15:56                 ` Juanma Barranquero
2003-05-27 22:41     ` Juanma Barranquero
2003-05-27 23:03     ` Jason Rumney
2003-05-27 23:22     ` Kenichi Handa

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=200305312033.h4VKXbcJ000827@rum.cs.yale.edu \
    --to=monnier+gnu/emacs@rum.cs.yale.edu \
    --cc=jmbarranquero@laley.wke.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 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).