Gnus development mailing list
 help / color / mirror / Atom feed
From: Laura Conrad <lconrad@world.std.com>
Subject: Re: A release, perhaps?
Date: 12 Apr 2000 10:23:28 -0400	[thread overview]
Message-ID: <kh7snwrtn33.fsf@acme47.nineco.com> (raw)
In-Reply-To: "David Z. Maze"'s message of "11 Apr 2000 20:46:12 -0400"

>>>>> "David" == David Z Maze <dmaze@mit.edu> writes:

    David> Traffic on gnu.emacs.gnus suggests that, if I upgrade to
    David> the latest CVS version of Gnus, all of my problems (at
    David> least with get-posting-charset) will be solved.  I've
    David> worked on enough projects to distrust this; an arbitrary
    David> snapshot of something out of CVS is as likely to work
    David> properly as to crash Emacs horribly every time I start it
    David> up.

I think it's a little better than that.  I did have a pretty bad
experience once since we've had the CVS, but I reported it promptly,
and the subsequent traffic suggested that if I hadn't, someone else
would have.  I think enough people are getting CVS pretty often and
using it pretty heavily that if you're:

        reading the ding list
        have the last stable version to go back to
        set mail-source-delete-incoming to nil

you should be pretty safe.

I was missing a couple of those points when I hit the bad version.
This is how I know to write the list.  If there are things I did right
without thinking about it that other people have found out about the
hard way, please add them to the list now.

    David> In the good old days of Gnus 5.6, there would be a Gnus
    David> release every week or two.  Not every release worked, but
    David> there was at least a semblance of quality control.  It'd
    David> certainly be nice to be able to periodically pull down a
    David> prerelease version of Gnus that's more reputable.

I agree with all of this, but not enough to volunteer to do the QA.  I
think the days when there were regular releases were also the days
when Lars was working something like full time on gnus.  What we have
in CVS is a lot of people doing small occasional fixes, which isn't
conducive to the kind of work that goes into a release with quality
control.

-- 
Laura (mailto:lconrad@world.std.com , http://www.world.std.com/~lconrad/ )
(617) 661-8097	fax: (801) 365-6574 
233 Broadway, Cambridge, MA 02139




      reply	other threads:[~2000-04-12 14:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-12  0:46 David Z. Maze
2000-04-12 14:23 ` Laura Conrad [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=kh7snwrtn33.fsf@acme47.nineco.com \
    --to=lconrad@world.std.com \
    /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.
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 NNTP newsgroup(s).