From: Joe Buck <jbuck@synopsys.com>
To: mmitchell@usa.net
Cc: egcs@cygnus.com
Subject: Re: 1.0.2 and 1.1 releases
Date: Sun, 15 Feb 1998 11:52:00 -0000 [thread overview]
Message-ID: <199802151951.LAA01892@atrus.synopsys.com> (raw)
In-Reply-To: <199802150924.JAA24175@quickstep.stanford.edu>
> I'm a bit concerned about the 1.0.2 release. In particular, we all
> have our pet peeves about 1.0.1. For HJ, it's that certain things
> don't work well on Linux, for me that certain C++ features cause
> crashes that we have since fixed, and we have to keep answering
> questions about the crashes, and for others I am sure there are other
> bug-a-boos.
I think that basic functionality on Linux should be fixed, as should
compiler crashes that can be fixed by a small change, and everything else
should wait. I think that this is not too different from what Mark is
saying.
> I think that there have been so many improvements since 1.0 that the
> right thing to do is get 1.0.2 out, fixing any truly egregious and
> horrible bugs that can be fixed with very simple changes (that's two
> criteria!), and then get 1.1 out pretty soon.
prev parent reply other threads:[~1998-02-15 11:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-02-15 9:21 Mark Mitchell
1998-02-15 9:29 ` Jeffrey A Law
1998-02-15 11:52 ` Joe Buck [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=199802151951.LAA01892@atrus.synopsys.com \
--to=jbuck@synopsys.com \
--cc=egcs@cygnus.com \
--cc=mmitchell@usa.net \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).