Andrea Aime wrote: >> Any objection to adding a note in the release guide that instructs to >> turn off mail notification for the batch update of pushing back open >> issues? Rationale is that it is a lot of issues to go through for those >> who watch jira closely. I do this when I release but realized I never >> added it to the guide. > > Not sure... reporters might want to know that their issues are being > pushed back
Mass Jira spam is an indication that the labelling system is broken (or at least, cracked). Until it is fixed, I think Justin is doing the right thing, and it should be documented. Perhaps we should encourage labelling with branches rather than tags? When someone sets fix-version 1.7.6, do they mean fix on 1.7.x? The problem is that when a patch is submitted, setting fix-version on a tag is speculation. The problem with dropping tags for fix-version is that end users will have trouble converting svn revisions back to release tags, so they won't know which release contains the fix. Ideas? -- Ben Caradoc-Davies <[email protected]> Software Engineer, CSIRO Exploration and Mining Australian Resources Research Centre 26 Dick Perry Ave, Kensington WA 6151, Australia ------------------------------------------------------------------------------ Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
