People keep filling in "fix release" when creating (or working on bugs). However, fix release really needs to be set only for resolved/closed issues ... and in fact, must be set then.
I noticed that a large number of issues were marked with a fix release of "5.3" but were not actually fixed; this lead to some problems generating accurate issue list for the 5.3 release notes page. I did some bulk updates and hopefully didn't screw anything up too bad. Firstly: please be careful; when working on bugs, make sure fix release is clear; only set fix release when closing/resolving a bug. Secondly: we need to decide on closing vs. resolving; generally, "resolved" means a fix has been committed, and "closed" means the committed fix has been verified. We tend to cut corners, and that's ok, as long as we're consistent. I think all issues should be closed. Lastly: anyone out there a JIRA wizard who can fix up our workflows to enforce the above? -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
