You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Victor Smirnov <vi...@uwc.ru> on 2000/01/28 13:25:52 UTC
Suggestions on Bug Tracking System arcitechture
Hello Jeremy!
IMO, the first principle of design for this is simplisity of implementation.
I'm almost sure that after some evaluation our Bug Tracking System
will be redesigned. So, for the beging lets make one for experiments:-)
I sugest to put each bug in separate XML file and organize them in directory
structure according to the bug state.
New term. Bugs' Library (or simple Library) - collection of bugs, organized
into directory structure according to their state.
May be one file is simpler, but on the other hand, having several files we
can experiment
with DTD and XSL. We can have slightly different format and way of
represantation for some
bugs.
Library can be published - it's converted to the proper format (html, txt,
etc.) and necessary indexes are added. Or it can be access online.
Sugested directory structure:
BugLibrary/submited Newly submited bugs, no action is taken on
them.
BugLibrary/new This bugs are properly handled (assigned
to the developer
and activated) and are in
working stage.
BugLibrary/resolved Bugs already fixed, resolution is given.
BugLibrary/closed Bugs fixed already in some release.
---
This is heavely based on the Life Cycle Of A Bug from Bugzilla.
(see http://www.mozilla.org/bugs/ )
The next step is the Bug DTD. I hope you don't mind if I write not DTD
but the example of the bug.
-- This is the first variant. Truely speaking I don't like this, at this
moment
-- I just whant to be sure that no data is missed.
--
-- The open question are
--
-- 1. where to place dependences between bugs -
-- separate file or in each bug?
--
-- 2. How to store history of changes?
-- Do we need to story history?
<bug id="123">
<resolution>open</resolution>
<!-- or may be fixed, etc. -->
<version>1.6.1-dev</version>
<component>FileProcessor</component>
<!-- Component name - the list of components is the
separate topic -->
<platform>PC</platform>
<os>Windows 98</os>
<priority>P1</priority>
<severity>major</severity>
<reporter>
<person name="Victor" mail="victor@uwc.ru"/>
<!-- maybe some other info, for instance expierence -->
</reporter>
<cc>
<person name="Alexey" mail="Alexey_Mendelev@net-burg.com"/>
<person name="Roman" mail="Roman.Verkhanovsky@usu.ru"/>
</cc>
<assigned>
<person DevID="SM"/>
</assigned>
<!-- :-) -->
<!-- Initial description by submiter -->
<short>Description in one line</short>
<dsc>Initial description of the bug
</dsc>
<whiteboard>
<comment>
<person name="Pussy" mail="cat@com"/>
<body>
Additional comment, may be several of them
</body>
</comment>
<attachment>
<person name="Pussy" mail="cat@com"/>
<type type="patch"/>
<body>
Their we can put patches, etc.
</body>
</attachment>
</whiteboard>
</bug>
Comments and suggestions will be appriciated.
- Victor
RE: Suggestions on Bug Tracking System arcitechture
Posted by Gerard van Enk <ge...@eo.nl>.
> The next step is the Bug DTD. I hope you don't mind if I write not DTD
> but the example of the bug.
>
>
> -- This is the first variant. Truely speaking I don't like this, at this
> moment
> -- I just whant to be sure that no data is missed.
> --
> -- The open question are
> --
> -- 1. where to place dependences between bugs -
> -- separate file or in each bug?
> --
> -- 2. How to store history of changes?
> -- Do we need to story history?
>
>
> <bug id="123">
>
> <resolution>open</resolution>
> <!-- or may be fixed, etc. -->
>
> <version>1.6.1-dev</version>
If Bugoon is to be used for bugtracking in other parts of Apache, you need
something like: <product>
<name>Cocoon</name>
<version>1.6.1-dev</version>
etc...
Gerard