On Sun, 12 Jul 2009, Jean-Marc Lasgouttes wrote:
> Note that bugs are first NEW, and become assigned when someone
> accepts them. We could add a new unconfirmed state.
Do we have some diagram or similar that illustrates the life cycle of
issues? Perhaps useful to show to people reporting bugs.
I do not think we have this.
I looked up the Trac documentation (see below), and first thought I'd redo
one of the diagrams. However, there's a script, showworkflow, that uses
Graphiz to generate a diagram. So, assuming that I used the correct
trac.ini, the diagram I created and embedded on the following page,
http://wiki.lyx.org/Devel/Administration#Trac_lifecycle
should be our current workflow. Could you (Jean-Marc) verify that it's
correct?
Similarly, are we writing a description of for what the different
components are to be used? For us it might be obvious, but perhaps not
to all.
No, we don't have this.
/Christian
Some links:
* Trac documentation
** About tickets - http://trac.edgewall.org/wiki/TracTickets
** About life cyle - http://trac.edgewall.org/wiki/TracWorkflow
(has diagrams, refers to more inside the Trac source etc)
--
Christian Ridderström Mobile: +46-8 768 39 44
