From: Tim Goodwin <tgoodwin@cygnus.co.uk>
To: rc@hawkwind.utcs.toronto.edu
Subject: Development snapshots now available
Date: Tue, 21 Jul 1998 12:17:08 -0400 [thread overview]
Message-ID: <KlYAABm/tDWJsgQA@nan.cygnus.co.uk> (raw)
As an experiment, I have started making "snapshots" of the development
version of rc available, so the brave and foolish can play with the
latest code that I am working on. The aim of this experiment is to make
the next beta release better, and happen sooner. If the snapshots don't
seem to be helping towards this cause, I will abandon the experiment.
The perceived problem that I'm trying to solve is this. It's a long
time since I released rc-1.5b2. A number of problems, some of them
serious, have come to light since that release and been fixed. However,
I'm not ready to make another beta release yet.
As you would expect, the snapshots come with no guarantees. Please only
download them if you are interested in working with buggy code. Please
don't use them to run life support machines, or nuclear power plants.
If you report a bug in rc---snapshot, beta, or full release---you can
expect to receive a reply saying "my fix is in the latest snapshot,
please pick it up and see if it fixes your problem". I don't intend to
announce every new snapshot to the list: if you want 'em, you know where
to find 'em.
The latest snapshot is here. As you would expect, subsequent snapshots
will be in the same directory. If you don't have access to FTP, then
you can't get snapshots. (Exception: if a snapshot fixes a bug that you
reported, I'll figure out some way to get it to you.)
ftp://ftp.cygnus.com/pub/tgoodwin/rc/snap/rc-1.5s19980721.tar.gz
Any thoughts, comments, or suggestions are most welcome.
Tim.
next reply other threads:[~1998-07-21 17:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-07-21 16:17 Tim Goodwin [this message]
1998-07-21 18:48 ` Tom Culliton
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=KlYAABm/tDWJsgQA@nan.cygnus.co.uk \
--to=tgoodwin@cygnus.co.uk \
--cc=rc@hawkwind.utcs.toronto.edu \
/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).