Hi, following up a conversation we had with Jody and his "short term planning" e-mail I'd like to propose a jira cleanup sprint on May 21 or May 28 (these are the dates me and Jody share that are still free).
We did a similar sprint in GeoServer back in december. The idea is that a group of developers go through the jiras (especially the old ones) and: - quickly close the ones we know are not applicable anymore, or that have been fixed in the meantime. Literally close down the issue if you already know the issue is no more relevant, without the need to manually trying it out - solicit more feedback from the users about issues that evenly don't have enough meat to be even checked for validity. If we don't get feedback we can then close them as "cannot reproduce" some time later In GeoServer that allowed to close something like 200 issues in a day: http://jira.codehaus.org/secure/ConfigureReport.jspa?atl_token=yzNRUjXE9D&projectOrFilterId=project-10311&periodName=daily&daysprevious=150&cumulative=false&versionLabels=all&selectedProjectId=10311&reportKey=com.atlassian.jira.plugin.system.reports%3Acreatedvsresolved-report&Next=Next Doing the same for GeoTools might be a little more difficult, as we don't have as people knowledgeable about all the code base, but maybe we could split up by module? There are 856 jiras open, I believe we can cut down to 700 without such a great of an effort. What do you think? Cheers Andrea -- Andrea Aime OpenGeo - http://opengeo.org Expert service straight from the developers. ------------------------------------------------------------------------------ _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
