[Webtest] Re: Bug trackin tool for webtest?
Lisa Crispin
webtest@lists.canoo.com
Fri, 07 Jan 2005 15:40:57 +0000
--NextPart_Webmail_9m3u9jl4l_27309_1105112457_0
Content-Type: text/plain
Content-Transfer-Encoding: 8bit
But thinking about it some more, and looking at recent postings (I'm way behind on reading my email, also getting behind in my WebTest version), if it works better for the developers who are working on WebTest, a bug tracking system is fine with me. It would be nice if the tracking system can provide some way to show how many people are experiencing problems because of a particular issue.
-- Lisa
-------------- Original message from lisa.crispin@att.net (Lisa Crispin): --------------
I personally haven't felt the need for a bug tracking tool for WebTest, but I only use the basic functionality, I'm not trying to do anything very sophisticated with it. I agree with Mittie, there really aren't so many bugs that the overhead of a bug tracking tool is worthwhile. Also, if there's a bug that affects a lot of people, there will be lots of postings to the mailing list about it, which will alert someone capable of fixing the bug that it's a high priority.
-- Lisa
-------------- Original message from "Dierk Koenig" <dierk.koenig@canoo.com>: --------------
> I used several bug-tracking tools (Remedy, ClearQuest, Peregrine,
> Bugzilla, Gnats, Jira) and I found them all more difficult to use
> than a mere Wiki Page.
> Sure, when you have to manage a large amount of bugs then you may
> need such a support, but I always felt that entering bugs is
> really complicated. What type of bug is it? What part of the
> system is concerned? What is its priority? and so on
> Most of the time I don't know what to fill in and what happens
> if I fill in nothing or something wrong.
>
> Watching the bug-fixing activities of an open-source project
> can definitely reveal something about the project.
> (Not only how active they are, but also how buggy the
> Software is.)
>
> cheers
> Mittie
>
> > -----Original Message-----
> > From: webtest-admin@lists.canoo.com
> > [mailto:webtest-admin@lists.canoo.com]On Behalf Of Marc Guillemot
> > Sent: Freitag, 7. Januar 2005 13:47
> > To: webtest@lists.canoo.com
> > Subject: [Webtest] Re: Bug trackin tool for webtest?
> >
> >
> > I fear that it's too basic and to complicated: to enter a bug a
> > user needs to create a new page as well as to update the
> > overview page.
> >
> > Furthermore, a bug tracking tool can be used by visitors to see
> > the activity of the project: how many issues opened and
> > fixed in the last x months.
> >
> > Marc.
> >
> > Dierk Koenig wrote:
> > > Hi,
> > >
> > > Yes, having such a tool is sometimes convenient.
> > >
> > > On the other hand, installation, maintenance, etc. again add
> > > to the workload. So it needs to pull its weight.
> > >
> > > Currently we only have few Bugs open in Canoo WebTest and everything
> > > that is not immediately solved and is in jeopardy of being lost
> > > can be added to
> > > http://webtest-community.canoo.com/wiki/space/Bug+Reports
> > > This solution has the additional benefit, that you can google for
> > > it.
> > >
> > > Do you think, we need more than that?
> > >
> > > cheers
> > > Mittie
> > >
> > >
> > >>-----Original Message-----
> > >>From: webtest-admin@lists.canoo.com
> > >>[mailto:webtest-admin@lists.canoo.com]On Behalf Of Marc Guillemot
> > >>Sent: Freitag, 7. Januar 2005 10:59
> > >>To: webtest@lists.canoo.com
> > >>Subject: [Webtest] Bug trackin tool for webtest?
> > >>
> > >>
> > >>Hi,
> > >>
> > >>what about making a bug tracking tool available on webtest website?
> > >>
> > >>Currently the problems reported on the mailing list have a high
> > >>risk to be lost if not quickly solved. A special tool (à
> > >>la bugziall, mantis, jira or other) would allow users to query
> > >>existing bug reports, to enter new ones if they find some
> > >>news issues and for developers it would give an overview of the
> > >>current problems.
> > >>
> > >>Marc.
> > >>
> > >>_______________________________________________
> > >>WebTest mailing list
> > >>WebTest@lists.canoo.com
> > >>http://lists.canoo.com/mailman/listinfo/webtest
> > >>
> >
> > _______________________________________________
> > WebTest mailing list
> > WebTest@lists.canoo.com
> > http://lists.canoo.com/mailman/listinfo/webtest
> >
>
> _______________________________________________
> WebTest mailing list
> WebTest@lists.canoo.com
> http://lists.canoo.com/mailman/listinfo/webtest
--NextPart_Webmail_9m3u9jl4l_27309_1105112457_0
Content-Type: text/html
Content-Transfer-Encoding: 8bit
<html>
<!-- BEGIN WEBMAIL STATIONERY -->
<head></head>
<body>
<!-- WEBMAIL STATIONERY noneset -->
<DIV></DIV>
<DIV>But thinking about it some more, and looking at recent postings (I'm way behind on reading my email, also getting behind in my WebTest version), if it works better for the developers who are working on WebTest, a bug tracking system is fine with me. It would be nice if the tracking system can provide some way to show how many people are experiencing problems because of a particular issue.</DIV>
<DIV>-- Lisa</DIV><BR>
<BLOCKQUOTE style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">-------------- Original message from lisa.crispin@att.net (Lisa Crispin): -------------- <BR><BR><!-- BEGIN WEBMAIL STATIONERY --><!-- WEBMAIL STATIONERY noneset -->
<DIV></DIV>
<DIV>I personally haven't felt the need for a bug tracking tool for WebTest, but I only use the basic functionality, I'm not trying to do anything very sophisticated with it. I agree with Mittie, there really aren't so many bugs that the overhead of a bug tracking tool is worthwhile. Also, if there's a bug that affects a lot of people, there will be lots of postings to the mailing list about it, which will alert someone capable of fixing the bug that it's a high priority. </DIV>
<DIV>-- Lisa</DIV><BR>
<BLOCKQUOTE style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">-------------- Original message from "Dierk Koenig" <dierk.koenig@canoo.com>: -------------- <BR><BR><BR>> I used several bug-tracking tools (Remedy, ClearQuest, Peregrine, <BR>> Bugzilla, Gnats, Jira) and I found them all more difficult to use <BR>> than a mere Wiki Page. <BR>> Sure, when you have to manage a large amount of bugs then you may <BR>> need such a support, but I always felt that entering bugs is <BR>> really complicated. What type of bug is it? What part of the <BR>> system is concerned? What is its priority? and so on <BR>> Most of the time I don't know what to fill in and what happens <BR>> if I fill in nothing or something wrong. <BR>> <BR>> Watching the bug-fixing activities of an open-source project <BR>> can definitely reveal something about the project. <BR>> (Not only how active they are, but also how buggy the <BR>> Software is.) <BR>> <BR>> cheers <BR>> Mittie <BR>> <BR>> > -----Original Message----- <BR>> > From: webtest-admin@lists.canoo.com <BR>> > [mailto:webtest-admin@lists.canoo.com]On Behalf Of Marc Guillemot <BR>> > Sent: Freitag, 7. Januar 2005 13:47 <BR>> > To: webtest@lists.canoo.com <BR>> > Subject: [Webtest] Re: Bug trackin tool for webtest? <BR>> > <BR>> > <BR>> > I fear that it's too basic and to complicated: to enter a bug a <BR>> > user needs to create a new page as well as to update the <BR>> > overview page. <BR>> > <BR>> > Furthermore, a bug tracking tool can be used by visitors to see <BR>> > the activity of the project: how many issues opened and <BR>> > fixed in the last x months. <BR>> > <BR>> > Marc. <BR>> > <BR>> > Dierk Koenig wrote: <BR>> > > Hi, <BR>> > > <BR>> > > Yes, having such a tool is sometimes convenient. <BR>> > > <BR>> > > On the other hand, installation, maintenance, etc. again add <BR>> > > to the workload. So it needs to pull its weight. <BR>> > > <BR>> > > Currently we only have few Bugs open in Canoo WebTest and everything <BR>> > > that is not immediately solved and is in jeopardy of being lost <BR>> > > can be added to <BR>> > > http://webtest-community.canoo.com/wiki/space/Bug+Reports <BR>> > > This solution has the additional benefit, that you can google for <BR>> > > it. <BR>> > > <BR>> > > Do you think, we need more than that? <BR>> > > <BR>> > > cheers <BR>> > > Mittie <BR>> > > <BR>> > > <BR>> > >>-----Original Message----- <BR>> > >>From: webtest-admin@lists.canoo.com <BR>> > >>[mailto:webtest-admin@lists.canoo.com]On Behalf Of Marc Guillemot <BR>> > >>Sent: Freitag, 7. Januar 2005 10:59 <BR>> > >>To: webtest@lists.canoo.com <BR>> > >>Subject: [Webtest] Bug trackin tool for webtest? <BR>> > >> <BR>> > >> <BR>> > >>Hi, <BR>> > >> <BR>> > >>what about making a bug tracking tool available on webtest website? <BR>> > >> <BR>> > >>Currently the problems reported on the mailing list have a high <BR>> > >>risk to be lost if not quickly solved. A special tool (à <BR>> > >>la bugziall, mantis, jira or other) would allow users to query <BR>> > >>existing bug reports, to enter new ones if they find some <BR>> > >>news issues and for developers it would give an overview of the <BR>> > >>current problems. <BR>> > >> <BR>> > >>Marc. <BR>> > >> <BR>> > >>_______________________________________________ <BR>> > >>WebTest mailing list <BR>> > >>WebTest@lists.canoo.com <BR>> > >>http://lists.canoo.com/mailman/listinfo/webtest <BR>> > >> <BR>> > <BR>> > _______________________________________________ <BR>> > WebTest mailing list <BR>> > WebTest@lists.canoo.com <BR>> > http://lists.canoo.com/mailman/listinfo/webtest <BR>> > <BR>> <BR>> _______________________________________________ <BR>> WebTest mailing list <BR>> WebTest@lists.canoo.com <BR>> http://lists.canoo.com/mailman/listinfo/webtest </BLOCKQUOTE><!-- END WEBMAIL STATIONERY --></BLOCKQUOTE>
<!-- END WEBMAIL STATIONERY -->
</body>
</html>
--NextPart_Webmail_9m3u9jl4l_27309_1105112457_0--