So what does a bug reporter do if they confirm the bug is fixed in a nightly? You seem to be suggesting that they do not provide the confirmed-fixed feedback usually indicated in Jira by closing the issue.
To make closing part of the release process (and I think that is a really good idea!) we need to start treating resolved as being confirmed-fixed (instead of closing the issue). This differs from the Jira manual. I think this is a worthwhile, but will require Jira user education. We need to identify the two use-cases: (1) reporter feedback, and (2) release manager changelog generation. In my view, we can't use "Closed" for both. You are asking us to choose (2). I agree. On 23/05/12 11:35, Justin Deoliveira wrote: > Come on... is closing issues before a release really that important? -- Ben Caradoc-Davies <ben.caradoc-dav...@csiro.au> Software Engineer CSIRO Earth Science and Resource Engineering Australian Resources Research Centre ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
