Jody Garnett wrote: > 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?
The main lesson that uDig has to share is that issues that don't have a scheduled fix version get forgotten. If on each release we have to actively shunt these bugs onto the next version, we see them. I recognize that i'm a hippocrite here, having not gotten around to getting the issues i'm maintainer for up-to-date. Do we have any plans of releasing 2.1.2? I see 65 bugs with this cited as the fix version, but don't think this reflects reality. I'm not requesting immediate action here -- just pointing out that this needs to be pulled together as 2.2 approaches, and 2.3/2.4 sneak in. I don't think dropping bugs because they are old is proper -- we should actually look at them, and decide on a case-by-case basis if they still apply. So... rant rant rant... the point being, let's *use* jira :) Cheers, Cory. 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
