I am strongly opposed to any mass changes of Jira issues. In my view, the most useful piece of information we have on many community-reported issue is the last-updated field. This is a direct measure of the liveness of the issue. Gratuitous tagging destroys this information, not to mention making work for yourself. I propose that we retag an issue only when it is reconfirmed as affecting that release or branch. This will occur naturally when users search for existing bugs before reporting new ones (or Andrea cleans up after them). I fear that any Jira cleanup is an indication that we are not being lazy enough. http://www.hhhh.org/wiml/virtues.html
Let sleeping issues lie. -- Ben Caradoc-Davies <[email protected]> Software Engineer, CSIRO Exploration and Mining Australian Resources Research Centre 26 Dick Perry Ave, Kensington WA 6151, Australia ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
