[LA-SiGMA-gpu] issue tracker

[Juana Moreno]

	This looks useful. And, I agree that a commit-mailing list will 
be also useful. Thank you!


On Thu, May 17, 2012 at 09:52:31AM -0500, Frank Loeffler wrote:
> On Thu, May 17, 2012 at 09:14:53AM -0500, Juana Moreno wrote:
> >      Could you send a short description about this tracker? I have never used one.	
> 
> An issue tracker can be seen as a 'database' within which you have items
> (issues / bug reports / however you like to call it). These items have
> some structure: they have a subject (like in an email) and a longer
> description. They can have some meta data attached. Examples are:
> 
> - 'component': This is usually used to easily differentiate between
>   different sub-projects. I created three for each sub-project of la-sigma.
> - 'priority': Can be used to mark some issues as particularly important
>   (or not)
> - 'type': Can currently be set to 'defect', 'enhancement' or 'task'
> - You can add a couple of more fields, but that's a bit too much for
>   this email and right now not really important for la-sigma.
> 
> All of the above can be easily configured, so let me know if you need
> changes.
> 
> These items usually have some 'life cycle', and how exactly that happens
> depends a lot on what you want. The simplest cycle would be that someone
> openes a report, and someone else closes it again when the problem is
> fixed. Alternatively the report can be marked as 'invalid', 'wontfix',
> 'duplicate' or 'worksforme' if this makes sense.
> 
> More complicated things are possible, but not really necessary. We
> should only spend a minimal time on that system and concentrate on the
> code itself. However, the issue tracker is a great tool to
> 
> - not forget about things you want to fix, but don't have the time now
> - which bugs are reported already (and may already be fixed)
> 
> Trac can be configured to send an email every time something changed
> (like a new ticket is opened, or an existing is commented on). Usually
> this is send to the commit-mailing list of the same project. I don't
> think la-sigma has one of these as of now. Would it be a good idea to
> create one? People can then subscribe / unsubscribe themselves when they
> (don't) want to receive these messages instead of every time asking IT
> support to add/remove them from the notifications.
> 
> In case you would like to see an example of a 'live' trac installation,
> take a look at
>    https://trac.einsteintoolkit.org/wiki
> I couldn't manage the Einstein Toolkit without it.
> 
> Frank
>