|
From: <ma...@fu...> - 2007-12-28 14:03:37
|
hi all, 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 later state. This way I won't forget about it, and when the issue is resolved I can easily close it. The proces is made more transparent as other people can see what issues are there and who is working on. Progress will be easier to see. Issue should be assigned to a specific category so developers can pick them up easily. I think issues can be kept more up to date in the tracker and issues will be more clear to the outside. I'm not sure about the the titles for the tracker categories. I think there are two directions: Global category names or Specific category names. 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. I want to propose the following tracker categories for bugs/issues: - None - Not sure - Frontend - html - css - Core - Wicket - Spring - Dao - Datebase (Hibernate) I hope you guys have some thoughts on this and maybe some remarks on my (proposed) approach and category names. cheers, Mattijs |