all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Juanma Barranquero" <lekktu@gmail.com>
To: "Eli Zaretskii" <eliz@gnu.org>
Cc: Chong Yidong <cyd@stupidchicken.com>, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Release schedule
Date: Sun, 22 Apr 2007 10:11:54 +0200	[thread overview]
Message-ID: <f7ccd24b0704220111q462c9338ua587b4a7f5c62811@mail.gmail.com> (raw)
In-Reply-To: <ufy6tgl7w.fsf@gnu.org>

On 4/22/07, Eli Zaretskii <eliz@gnu.org> wrote:

> So I think we need another pretest, but if I'm the only one, so be it.

You're not the only one. It wouldn't be the first time that apparently
trivial changes bite us. Releasing without testing seems a bit
reckless, and it's not like a few days more will even be noticeable
against our quinquennial-release backdrop.

So I'm all for another pretest.

             Juanma

  reply	other threads:[~2007-04-22  8:11 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-20 21:53 Release schedule Richard Stallman
2007-04-21  3:38 ` Chong Yidong
2007-04-21 10:11 ` Eli Zaretskii
2007-04-21 19:25   ` Chong Yidong
2007-04-21 20:02     ` Glenn Morris
2007-04-21 20:14       ` Chong Yidong
2007-04-21 20:17         ` Glenn Morris
2007-04-21 22:31       ` Nick Roberts
2007-04-21 23:02         ` Glenn Morris
2007-04-22  3:08     ` Eli Zaretskii
2007-04-22  8:11       ` Juanma Barranquero [this message]
2007-04-22 10:33         ` Kim F. Storm
2007-04-22 11:13           ` David Kastrup
2007-04-23  3:48             ` Richard Stallman
2007-04-23  5:13               ` Stefan Monnier
2007-04-23  6:12                 ` David Kastrup
2007-04-22 11:51           ` Romain Francoise
2007-04-22 14:20       ` Chong Yidong
2007-04-22 22:56       ` Kenichi Handa
2007-04-22 16:35     ` Richard Stallman
2007-04-22 20:42       ` Eli Zaretskii

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f7ccd24b0704220111q462c9338ua587b4a7f5c62811@mail.gmail.com \
    --to=lekktu@gmail.com \
    --cc=cyd@stupidchicken.com \
    --cc=eliz@gnu.org \
    --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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.