Hi Cory, follow up to your agenda item about Jira. I recently organized the jira components, providing them with a consistent set of names etc.. and where know I have Jira automatically assign a bug to the admin for each component.
It seems we only have three bugs that are not assigned a component (fixing that now), going to see if I can make that required. If assigned a component the bug should be assigned to the associated module maintainer ... Other steps we can take: - use jira to organize our next couple releases (results of GC and FM branch merges) - update the schedule by which bugs are fixed (226 unscheduled), may need a solid road map for that. - 1/3 of bugs are about learning/demo/rendering, (eg http://jira.codehaus.org/browse/GEOT-863) we may considering cutting library scope - mark any bug as wont fix that has not had any action in two years? Module maintainers may find it useful to set up their Jira "workbench" to shown them the open bugs for their modules (and/or) assigned to them. Jody PS. Another suggestion is to use Jira as your home page. Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
