Agreed that culling renaming is needed; but also adding (since we have some modules like "process" and "wps" that are not represented.
It is easier for us to track bugs according to what module they are in - however that is harder for users to report against. Hopefully they can report against what module they find the issue in at least? A different approach is the component list for uDig, we made the decisions to drastically lower the number of "components" and renamed them to match the user experience and not the codebase. - https://jira.codehaus.org/browse/UDIG#selectedTab=com.atlassian.jira.plugin.system.project%3Acomponents-panel This solution works for a product, but not so much for a library. Jody On 23/05/2010, at 12:16 PM, Michael Bedward wrote: > Hi Jody, > >> - issues that are not assigned to any component >> >> The last one is interesting and my focus for the day - these are the issues >> that are not >> likely to be noticed by a module maintainer (or anyone!). I wish we could >> mark this field >> as mandatory... > > I think a culling / renaming session on the list of modules that > people see when creating an issue might help too. > > Michael ------------------------------------------------------------------------------ _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
