all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Releasing Emacs 22.2
Date: Fri, 03 Aug 2007 09:54:57 +0200	[thread overview]
Message-ID: <86ir7xjbn2.fsf@lola.quinscape.zz> (raw)
In-Reply-To: <jwv7iodxi0b.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Fri\, 03 Aug 2007 02\:15\:44 -0400")

Stefan Monnier <monnier@iro.umontreal.ca> writes:

>>> I hope to release Emacs 22.2 in a few weeks,
>>     I hope there was a "a pretest of" missing above.
>
>> I am not sure a pretest is needed, with a few new packages and a few
>> dozen bug fixes.  But it can't hurt.  However, all that is a side
>> issue.
>
> The new VC backends are all activated, so their code is executed every time
> a file is opened: there's a good chance that some bug in there will
> cause problems.  I've just fixed such a bug in vc-bzr yesterday.
>
>> The main point is that people need to fix the bugs
>> in order to make Emacs 22.2 possible at all.
>
>
>         Stefan
>
>
> PS: of course, we could disable the new VC backend by default, so as to
> avoid those risks.

I am against it.  I think that 22.1 has been good enough that the
tradeoff between release cycles and quality should not get out of
hand.  We should not miss the change to get some Emacs with packages
corresponding to the state of software development of 2007 out and get
people excited about Emacs again before tackling the architectual
changes and corresponding release cycles.

-- 
David Kastrup

      reply	other threads:[~2007-08-03  7:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-02 15:46 Releasing Emacs 22.2 Richard Stallman
2007-08-02 17:18 ` Stefan Monnier
2007-08-03  3:37   ` Richard Stallman
2007-08-03  6:15     ` Stefan Monnier
2007-08-03  7:54       ` David Kastrup [this message]

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=86ir7xjbn2.fsf@lola.quinscape.zz \
    --to=dak@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --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.