From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: Volker Reichelt <reichelt@igpm.rwth-aachen.de>
Cc: dberlin@dberlin.org, gcc@gcc.gnu.org, bangerth@ices.utexas.edu,
giovannibajo@libero.it
Subject: Re: Suggested Bugzilla improvements
Date: Tue, 13 May 2003 10:20:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.53.0305131110060.24826@kern.srcf.societies.cam.ac.uk> (raw)
In-Reply-To: <200305130912.h4D9C7NZ015395@relay.rwth-aachen.de>
On Tue, 13 May 2003, Volker Reichelt wrote:
> * Version: By now, one can only select one version. The bugs, however,
> usually appear in more than one compiler version.
> Would it be possible to change that into a text field or to rename it
> into "Initial version"? Or are there better suggestions?
We have at present a full version number field (with date), which is
converted into the version number only field (for searching) and the full
version number inserted in the text (so we can tell which of the very wide
range of compilers calling themselves "3.3" the bug was reported against).
But tracking which set of versions a bug applies in seems to be a
difficult problem for bug tracking systems in general.
Also, what's happened to the various minor versions that were in the
version list? We did have 2.95.[1234], 3.0.[12345], 3.2.[123] included as
possible short version numbers - and there is documentation in
releasing.html / branching.html of when and how to add new numbers when
releasing and branching - but they are no longer available, although the
minor versions 3.1.1 and 3.1.2 are.
Didn't someone request that the keywords with legal/illegal in them should
be changed to use the GNUically correct terminology valid/invalid as part
of the conversion?
--
Joseph S. Myers
jsm28@cam.ac.uk
next prev parent reply other threads:[~2003-05-13 10:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-13 9:19 Volker Reichelt
2003-05-13 10:20 ` Joseph S. Myers [this message]
2003-05-13 14:39 ` Daniel Berlin
2003-05-13 14:52 ` Joseph S. Myers
2003-05-13 15:33 ` Daniel Berlin
2003-05-13 14:41 ` Daniel Berlin
2003-05-13 16:07 Volker Reichelt
2003-05-13 16:53 ` Daniel Berlin
2003-05-13 20:50 ` Joseph S. Myers
2003-05-14 15:07 ` Gerald Pfeifer
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=Pine.LNX.4.53.0305131110060.24826@kern.srcf.societies.cam.ac.uk \
--to=jsm28@cam.ac.uk \
--cc=bangerth@ices.utexas.edu \
--cc=dberlin@dberlin.org \
--cc=gcc@gcc.gnu.org \
--cc=giovannibajo@libero.it \
--cc=reichelt@igpm.rwth-aachen.de \
/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).