On 12 September 2011 12:59, Søren Hauberg <so...@hauberg.org> wrote: > man, 12 09 2011 kl. 12:48 +0100, skrev Carnë Draug: >> On 12 September 2011 12:34, Søren Hauberg <so...@hauberg.org> wrote: >> > man, 12 09 2011 kl. 11:58 +0100, skrev Carnë Draug: >> >> I can do that no problem. Is one category per package enough? >> > >> > I'm a bit slow... you want to create one category in the bug tracker per >> > package? Say we have 50 packages you want to create 50 categories in the >> > tracker? >> >> Yes. They all appear in the same tracker, it's just a way to filter >> them. I don't see a way to tag a bug report with the package names. It >> seems that each bug report can be part of a categorie and group. These >> are independent of each other so it's not possible to have different >> categories contained in each group or vice-versa. It is possible >> though to have one group per package and the categories split into >> different type of bugs (documentation, code optimization, wrong >> results, function extension, etc...). > > Ok. Won't this be a lot of work to maintain?
Hopefully when someone reports a bug they will enter the right package name. If not, I don't think a bug requires a category or group. Currently I can't think of another logical organization. It didn't even occur to me that there could be another way to group them. If someone has a more manageable organization it would be great. Maybe create a group for each of the most common packages (signal, control and image) and another group for all others (named 'other packages')? As new bugs are reported for packages without group, I can create the group. For example, I don't think I ever heard of anyone reporting bugs or even asking help for the bioinfo package. Carnë ------------------------------------------------------------------------------ Doing More with Less: The Next Generation Virtual Desktop What are the key obstacles that have prevented many mid-market businesses from deploying virtual desktops? How do next-generation virtual desktops provide companies an easier-to-deploy, easier-to-manage and more affordable virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/ _______________________________________________ Octave-dev mailing list Octave-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/octave-dev
