From: Romain Lenglet <rlenglet@domain.hid>
To: xenomai@xenomai.org
Subject: Re: [Xenomai-core] Bug tracker.
Date: Thu, 13 Oct 2005 15:08:21 +0900 [thread overview]
Message-ID: <200510131508.22053.rlenglet@domain.hid> (raw)
In-Reply-To: <434DEDDD.4020607@domain.hid>
> I'm not stronly opposing, but in my opinion it causes
> information to scatter in contrast to the ml. There'll be bug
> reports on the ml regardless of having or not having a bug
> tracking system in function. It's more difficult to
> follow/search two places than one. And this project isn't the
> size of openoffice or debian, so maybe the ml doesn't get
> cluttered by incoming bug reports. And finally, many bug
> reports already contain a reasonable fix and their tracking
> summarizes to "Applied." There are benefits, too, of course,
> like forcing a good format for a report.
One point in favor of the use of a tracker like that of Gforge or
GNA, is that it assigns a unique number to every bug / wish,
which could then be easily referenced in Changelogs, CVS/SVN
commits, etc.
It is easier to track bugs and have an history (when that bug has
been reported? when has it been fixed? etc. which is not always
clear from a ML).
I see it as complementary to the ML.
(my 2-yen contribution)
--
Romain Lenglet
next prev parent reply other threads:[~2005-10-13 6:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-12 21:04 [Xenomai-core] Bug tracker Gilles Chanteperdrix
2005-10-13 5:17 ` Heikki Lindholm
2005-10-13 6:08 ` Romain Lenglet [this message]
2005-10-13 6:21 ` Gilles Chanteperdrix
2005-10-13 6:35 ` Heikki Lindholm
2005-10-13 7:10 ` Gilles Chanteperdrix
2005-10-13 7:28 ` Heikki Lindholm
2005-10-13 23:30 ` Gilles Chanteperdrix
2005-10-14 5:56 ` Heikki Lindholm
2005-10-14 7:22 ` Gilles Chanteperdrix
2005-10-14 6:17 ` Heikki Lindholm
2005-10-14 7:31 ` Gilles Chanteperdrix
2005-10-14 18:32 ` Gilles Chanteperdrix
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=200510131508.22053.rlenglet@domain.hid \
--to=rlenglet@domain.hid \
--cc=xenomai@xenomai.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.