|
From: Zoran K. <zo...@fu...> - 2008-01-03 08:07:29
|
> I was busy reorganising the wiki a bit, when I came across the OpenIssues > page. On this page I saw a huge list of issues that have to be fixed. But > when I started reading some of the issues, some of them were already fixed > or are not applicable anymore. > > I would like to see that issues are posted in the tracker instead of the > wiki. I find it helpfull if i can report an issue i'm going to fix in a Obviously the best place is the tracker. Nice merciless refactoring :) > (...) > I guess it would be smart to use a bit of both. Bugs can be reported > without assigning them to a category. Once a developer picks up the bug > and finds out (throught the reporter) what the issue is, he can assign it > to a specific category. And the bug/issue can be fixed. Good process. > I want to propose the following tracker categories for bugs/issues: > > - None > - Not sure Why both of them? Can't the default be Not sure? > - Frontend > - html > - css > - Core > - Wicket > - Spring > - Dao > - Datebase (Hibernate) Perhaps make it technology independent? I.e. layers: presentation, service, data. What do the other developers and testers think? Best, Zoran -- Zoran Kovacevic Func. Internet Integration W http://www.func.nl M +31 6 48104284 T +31 20 4230000 F +31 20 4223500 GPG http://www.func.nl/keys/z.k...@fu... |