unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Thien-Thi Nguyen <ttn@glug.org>
Cc: emacs-devel@gnu.org
Subject: Re: Feature freeze (was Re: font-lock-comment-delimiter-face)
Date: Sun, 24 Apr 2005 17:46:40 -0400	[thread overview]
Message-ID: <E1DPow4-0003QA-DU@mail.agora-net.com> (raw)
In-Reply-To: <8ebr83q5rw.fsf_-_@xpc14.ast.cam.ac.uk> (message from Glenn Morris on Sun, 24 Apr 2005 21:27:47 +0100)

   From: Glenn Morris <gmorris+emacs@ast.cam.ac.uk>
   Date: Sun, 24 Apr 2005 21:27:47 +0100

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

that depends on the precise release methodology, which hasn't been
captured under admin/ or admin/notes/, as far as i can tell.  perhaps
that action (and even the term "capture") goes against the hacker way,
even though it is accepted in other organizational structures...

at this time there is a frustration from people who have a backlog of
changes they would like to commit, but have refrained from doing so,
especially when they see the continuing drizzle of commits done by
others.

perhaps the well-restrained can help the drizzlers to taper off by
showing how they keep their backlog maintained (but ready for commit
once the next release is made), while working on the items in the file
FOR-RELEASE.  the idea is not to stem the hacking, but to buffer it in
such a way that rms' release-threshold criteria can be met, even though
we don't know the criteria fully.

thi

  reply	other threads:[~2005-04-24 21:46 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   ` Feature freeze (was Re: font-lock-comment-delimiter-face) Glenn Morris
2005-04-24 21:46     ` Thien-Thi Nguyen [this message]
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=E1DPow4-0003QA-DU@mail.agora-net.com \
    --to=ttn@glug.org \
    --cc=emacs-devel@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).