From: Brian Gough <bjg@network-theory.co.uk>
To: gsl-discuss@sources.redhat.com
Subject: Re: 0.9.4 -> 1.0
Date: Wed, 19 Dec 2001 13:20:00 -0000 [thread overview]
Message-ID: <15308.42663.631709.203764@debian> (raw)
In-Reply-To: <3BCC4FDA.C2819D75@jpl.nasa.gov>
Edwin Robert Tisdale writes:
> Brian Gough wrote:
> > I'm preparing an 0.9.4 release from the current CVS. > Assuming
> there are no immediate problems, > I propose that it be retagged
> and released as 1.0. > According to my records all the reported
> bugs are fixed now.
> So what's next?
I envisage a long period of fixing bugs that emerge.
> Is the GSL finished? Or do you plan to begin work on 2.0?
I don't personally have any plans to work on a "2.0" version at the
moment.
next prev parent reply other threads:[~2001-12-19 13:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-19 13:20 Edwin Robert Tisdale
2001-12-19 13:20 ` Brian Gough [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-12-19 13:20 Brian Gough
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=15308.42663.631709.203764@debian \
--to=bjg@network-theory.co.uk \
--cc=gsl-discuss@sources.redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).