From: Yngve Svendsen <yngve.svendsen@sun.com>
To: Robert Inder <robert@interactive.co.uk>, help-gnats@gnu.org
Cc: andrewg@gnu.org
Subject: Re: Gnats Status
Date: Tue, 27 May 2003 10:25:00 -0000 [thread overview]
Message-ID: <5.2.1.0.0.20030527121439.032fd098@ms-etro01-01.norway.sun.com> (raw)
In-Reply-To: <f517k8cemhl.fsf@3lg.org>
At 11:02 27.05.2003 +0100, Robert Inder wrote:
>On the Gnats home page at
>
> http://www.gnu.org/software/gnats/
>
>you say apparently contradictory things.
>
>Under "GNATS news", you say...
>
> December 2, 2002: The second beta release of GNATS 4.0 is available
> for download.... This version shouldn't be considered ready for
> production use.
>
>But further down, under "Downloading GNATS", you say...
>
> The last "official" version is 3.113. If you are creating a new
> GNATS installation, we recommend you to use the current development
> version of GNATS 4.
>
>I am creating a new installation, but it is for "production" use
>by a small, "friendly" but distributed user community of around half a
>dozen people.
>
>Which version should I use?
My advice is that you should go with version 4, and I would say that 4.0
beta 2 is "more ready" for production use than the 3.11x versions ever
were. In fact, if you look closely in the 3.113 documentation, you will see
that 3.113 is actually also a beta version.
That's not to say that 4.0 beta 2 doesn't have problems and peculiarities
of its own, but most of them have workarounds, and I would say 4.0 beta 2
is the most stable and especially the most powerful GNATS there's ever been.
Yngve Svendsen
Gnatsweb maintainer
_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://mail.gnu.org/mailman/listinfo/help-gnats
prev parent reply other threads:[~2003-05-27 10:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-27 10:09 Robert Inder
2003-05-27 10:25 ` Yngve Svendsen [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=5.2.1.0.0.20030527121439.032fd098@ms-etro01-01.norway.sun.com \
--to=yngve.svendsen@sun.com \
--cc=andrewg@gnu.org \
--cc=help-gnats@gnu.org \
--cc=robert@interactive.co.uk \
/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).