public inbox for gnats-announce@sourceware.org
 help / color / mirror / Atom feed
From: Yngve Svendsen <yngve.svendsen@clustra.com>
To: gnats-announce@sources.redhat.com
Cc: bug-gnats@gnu.org, gnats-devel@sources.redhat.com
Subject: Announcing gnatsweb 2.9.1
Date: Thu, 11 Oct 2001 10:36:00 -0000	[thread overview]
Message-ID: <5.1.0.14.2.20011011173816.00b4f420@10.10.1.1> (raw)

A new release of Gnatsweb is available for download.

The version number is 2.9.1. This is mainly a bug fix release incorporating 
several small patches submitted over the last few months. A couple of minor 
features were also added.

Gnatsweb 2.x won't work with the upcoming Gnats 4. Versions working with 
Gnats 4 will have version numbers starting with a '4'. Patches and 
contributions for version 2.x are still welcome, even though no further 
releases are currently planned. The Gnatsweb 2.9.1 distribution (64 kB) is 
available at ftp://ftp.gnu.org/pub/gnu/gnatsweb/ immediately.

Below is the entry for 2.9.1 in the NEWS file of the distribution. For 
details, see the ChangeLog file.

Changes from 2.9.0 to 2.9.1
* Documentation corrected and significantly expanded.  We now provide
   a TROUBLESHOOTING document as well.
* Bug fix. E-mail address extraction for the "send email to interested
   parties" is now more robust.
* Bug fix. Handle browsers without Javascript support better.
* Bug fix. Minor problems with browsers such as Konqueror should be
   gone.
* Minor new feature: We now use both the category name and description
   and the responsible name and full name in dialogs on the create,
   edit and query pages.
* Minor new feature: Whether the Audit Trail is visible by default in
   the View PR screen is now configurable.
* Minor new feature: There is now a checkbox in the query pages which
   provides for displaying the current date on the query results page.

Yngve Svendsen
Gnatsweb maintainer

                 reply	other threads:[~2001-10-11 10:36 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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.1.0.14.2.20011011173816.00b4f420@10.10.1.1 \
    --to=yngve.svendsen@clustra.com \
    --cc=bug-gnats@gnu.org \
    --cc=gnats-announce@sources.redhat.com \
    --cc=gnats-devel@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).