Definition of Mantis workflow?

Ken Causey ken at kencausey.com
Tue Mar 1 20:22:02 UTC 2005


Hey Ned,

Looks like you have been spending time thinking about Mantis.  In the
very near future the Janitors project will be spawning a small sub-team
to discuss what improvements can be made to Mantis in the short term to
make it easier and clearer to use, particularly to newcomers.  Would you
be interested in participating in that group?  Perhaps even chairing it?
If so please subscribe to the janitors mailing list
( http://discuss.squeakfoundation.org/cgi-bin/ezmlm-cgi?8 ) and express
your interest.

Ken

On Tue, 2005-03-01 at 11:25 -0800, Ned Konz wrote:
> It's not clear to me how we're supposed to map the use of Mantis to our 
> workflow.
> 
> This should be documented, perhaps in such a way that clicking the "Docs" link 
> in Mantis actually explains something, instead of displaying an empty page.
> 
> What do the various choices mean for severity, status, and resolution?
> 
> How do changes to these choices relate to specific actions by members of our 
> community?
> 
> For instance:
> 
> When someone posts a fix to Mantis, what is the status and resolution supposed 
> to be set to?
> 
> How does one choose between "minor" and "major" severity?
> 
> When someone tests a proposed fix and wants to recommend that it gets applied 
> to the update stream (i.e. harvests it), how should the bug fields change? 
> Should this become "resolved"?
> 
> When a fix goes to the update stream, how should the bug fields change? Should 
> this be "resolved" -> "closed"?
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20050301/cbe043e6/attachment.pgp


More information about the Squeak-dev mailing list