[uportal-dev] Jira Issue Scheduling

[Eric Dalquist]

Just want to make a request, when you create jira issues please make sure they at least have either an affects or fix-for version. Even better would be for all new issues to have a fix-for version. Any small changes (patches, ui tweaks, minor enhancements) should get scheduled for the next patch release of each version they make sense in. If it is a bigger change and you're not sure about a fix-for version leave it blank but email this list with a link to the issue asking what the fix-for version should be.

If folks would like I can look at sticking this in the wiki.

Thanks,
-Eric

Jira issues without fix-for versions get forgotten and just add confusion at some point in the future when they are found and the original intent is not as clear. On the resolution side of issues, if you are working on an issue with a fix-for of 3.2.5 and 4.0.2 but you only fix it in trunk (lets say the fix is easy there but hard in the 3.2 branch). Clone the issue and set the fix-for on one to 4.0.2 and on the clone to 3.2.5 then resolve the 4.0.2 issue. That lets us track that the issue was fixed in 4.0 but that it still affects 3.2.

smime.p7s
Description: S/MIME Cryptographic Signature