[vtk-developers] VTK bug tracker hackaton logistics

David E DeMarle dave.demarle at kitware.com
Wed Oct 1 15:11:06 EDT 2014


David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909

On Wed, Oct 1, 2014 at 2:19 PM, Sean McBride <sean at rogue-research.com>
wrote:

> On Wed, 1 Oct 2014 12:32:19 -0400, David E DeMarle said:
>
> >see "the vtk software process"
> >https://docs.google.com/a/kitware.com/document/d/1nzinw-
> >dR5JQRNi_gb8qwLL5PnkGMK2FETlQGLr10tZw/edit
> >section 6
> >
> >"tabled" is something mantis keeps on putting in there for some reason I
> >don't understand. Think of it as backlog.
>
> OK, so it says one should set fixed bugs to 'closed'.  Then the submitter
> reopens if he disagrees I guess?  Are you sure submitters can reopen?  From
> what I've seen of Mantis, once set to 'closed' you need higher permission
> to reopen or even comment...
>
>
That is a configuration setting, just like the workflow states. On VTK,
developers, managers and the administrator can reopen bugs. I'll add
reporter and viewer as well.


> That doc also says "When a new bug report is made, mantis sends it off to
> the developer’s mailing list".  That doesn't seem to be true... perhaps it
> should be...?
>

Still seems to be coming through:

http://markmail.org/search/vtk-developers+list:org%2Evtk%2Evtk-developers+mantis+from:%22Mantis+Bug+Tracker%22+order:date-backward

Now the part about "the release manager reads all newly submitted bugs and
asks developers who are familiar with the area of VTK that the bug relates
to to do a cursory review" hasn't been working so well.



>
> Cheers,
>
> --
> ____________________________________________________________
> Sean McBride, B. Eng                 sean at rogue-research.com
> Rogue Research                        www.rogue-research.com
> Mac Software Developer              Montréal, Québec, Canada
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/vtk-developers/attachments/20141001/49067729/attachment-0002.html>


More information about the vtk-developers mailing list