unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Glenn Morris <gmorris+emacs@ast.cam.ac.uk>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Feature freeze (was Re: font-lock-comment-delimiter-face)
Date: Sun, 24 Apr 2005 21:27:47 +0100	[thread overview]
Message-ID: <8ebr83q5rw.fsf_-_@xpc14.ast.cam.ac.uk> (raw)
In-Reply-To: <m3ekd0582r.fsf@kfs-l.imdomain.dk> (Kim F. Storm's message of "Sun, 24 Apr 2005 20:43:40 +0200")

Kim F. Storm wrote:

> Feature freeze ?
[...]
> Can people please work on completing the release...

This prompts me to ask, when were the details of a feature freeze
agreed upon? I'm not trying to be provocative, but rather to suggest
that one reason for the continued delay is (IMO), lack of a clear
policy.

I'm aware of Kim's mail from 08 April last year ("It is time for a
feature freeze (it is NOW or never)",
<http://lists.gnu.org/archive/html/emacs-devel/2004-04/msg00176.html>),
which was clearly very prescient in its negative predictions (sadly).

This was a "we *should* do this" kind of email. But where was the
official announcement, "it's been decided, we *will* do this"? In
other words, a widely publicized announcement saying, eg: As of date X
there will be a feature freeze. After this date, do not do A, B, C.
Instead, concentrate on D, E, F.

If I missed it, I apologize, but a quick search of the archives didn't
find it. Maybe there is some implicit convention inherited from
previous occasions, but I think Emacs has acquired many new CVS
contributors (such as myself) since the last release, and hopefully
will continue to do so in future, so explicitness would be good, I
feel.


Also, shouldn't there also be a new branch for the release?
admin/notes/BRANCH says:

    This is the "HEAD" branch, otherwise known as the "trunk"
    ...
    The closure process for this branch is undocumented; concepts such
    as "freeze", "release", or "integration with the trunk" are not
    applicable to this branch.


This is all water under the bridge really, and I don't want to cause
more wasteful discussion, so by all means ignore this message. I'm just
saying:

1) with hindsight (or with foresight for the next time round), a clear
   statement of release policy would seem essential. Maybe it would
   even help now to make a such a statement.

2) should there be a new CVS branch for the release?

  reply	other threads:[~2005-04-24 20:27 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-23 22:51 font-lock-comment-delimiter-face Richard Stallman
2005-04-24  9:59 ` font-lock-comment-delimiter-face Eli Zaretskii
2005-04-24 18:43 ` font-lock-comment-delimiter-face Kim F. Storm
2005-04-24 20:27   ` Glenn Morris [this message]
2005-04-24 21:46     ` Feature freeze (was Re: font-lock-comment-delimiter-face) Thien-Thi Nguyen
2005-04-24 21:56       ` Eli Zaretskii
2005-04-26 10:05       ` Richard Stallman
2005-04-25 16:05   ` font-lock-comment-delimiter-face Richard Stallman
2005-04-25 22:20     ` font-lock-comment-delimiter-face Luc Teirlinck
2005-04-26 20:58 ` font-lock-comment-delimiter-face Stefan Monnier
2005-05-11 16:25   ` font-lock-comment-delimiter-face Richard Stallman
2005-05-11 19:51     ` font-lock-comment-delimiter-face Stefan Monnier
2005-05-13  1:34       ` font-lock-comment-delimiter-face Richard Stallman
2005-05-13  3:45         ` font-lock-comment-delimiter-face Stefan Monnier
2005-05-14  0:26           ` font-lock-comment-delimiter-face Richard Stallman
2005-05-13  4:11     ` font-lock-comment-delimiter-face Stefan Monnier
2005-05-13  8:21       ` font-lock-comment-delimiter-face Kim F. Storm
2005-05-13 13:15         ` font-lock-comment-delimiter-face Eli Zaretskii
2005-05-13 13:36           ` font-lock-comment-delimiter-face David Kastrup
2005-05-13 19:27             ` font-lock-comment-delimiter-face Edward O'Connor
2005-05-13 20:50               ` font-lock-comment-delimiter-face Daniel Brockman
2005-05-14  0:25       ` font-lock-comment-delimiter-face Richard Stallman
2005-05-14  1:25         ` font-lock-comment-delimiter-face Nick Roberts
2005-05-14 15:12           ` font-lock-comment-delimiter-face Richard Stallman
2005-05-14 22:43             ` font-lock-comment-delimiter-face Nick Roberts
2005-05-14 23:55               ` font-lock-comment-delimiter-face Paul Pogonyshev
2005-05-15  9:48               ` font-lock-comment-delimiter-face David Kastrup
2005-05-15 22:39                 ` font-lock-comment-delimiter-face Richard Stallman
2005-05-15 22:50                   ` font-lock-comment-delimiter-face David Kastrup
2005-05-16 19:28                     ` font-lock-comment-delimiter-face Richard Stallman
2005-05-17 20:09                       ` font-lock-comment-delimiter-face Edward O'Connor
2005-05-18 22:44                         ` font-lock-comment-delimiter-face Richard Stallman
2005-05-19  0:01                           ` font-lock-comment-delimiter-face Lute Kamstra
2005-05-19 13:02                           ` font-lock-comment-delimiter-face Stefan Monnier
2005-05-19 14:44                             ` font-lock-comment-delimiter-face Stefan Monnier
2005-05-19 15:01                               ` font-lock-comment-delimiter-face Kim F. Storm
2005-05-20 21:57                               ` font-lock-comment-delimiter-face Richard Stallman
2005-05-19 15:01                             ` font-lock-comment-delimiter-face Kim F. Storm
2005-05-19 15:46                               ` font-lock-comment-delimiter-face David Kastrup
2005-05-19 16:52                           ` font-lock-comment-delimiter-face Dan Nicolaescu
2005-05-20 21:56                             ` font-lock-comment-delimiter-face Richard Stallman
2005-05-21 17:51                               ` font-lock-comment-delimiter-face Dan Nicolaescu
2005-05-15 15:58               ` font-lock-comment-delimiter-face Richard Stallman
2005-05-18 18:02                 ` font-lock-comment-delimiter-face Romain Francoise
2005-05-14 16:11     ` font-lock-comment-delimiter-face Ralf Angeli
2005-05-15 15:59       ` font-lock-comment-delimiter-face Richard Stallman
2005-05-15 17:34         ` font-lock-comment-delimiter-face Ralf Angeli
2005-05-16  3:55           ` font-lock-comment-delimiter-face Richard Stallman
2005-05-16  8:16             ` font-lock-comment-delimiter-face Ralf Angeli
2005-05-16 21:20               ` font-lock-comment-delimiter-face Richard Stallman
2005-05-17  7:30                 ` font-lock-comment-delimiter-face Ralf Angeli
2005-05-18 23:22                   ` font-lock-comment-delimiter-face 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=8ebr83q5rw.fsf_-_@xpc14.ast.cam.ac.uk \
    --to=gmorris+emacs@ast.cam.ac.uk \
    --cc=emacs-devel@gnu.org \
    --cc=rms@gnu.org \
    /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).