Re: JIRA versions 2.0.x & 2.1.x

[Donald Woods]

Thought these were to be used to keep everything out of a generic Future bucket, but it has never worked, so +1 to removing them.

-Donald


Joe Bohn wrote:

BTW - Shouldn't the Fix Version field remain blank until someone either starts working on the issue or code is integrated into svn?

What is the value of JIRA versions 2.0.x and 2.1.x? Having these makes it difficult to track changes per release. For example, when a JIRA is resolved in branches/2.1 intended for a 2.1.2 release - we should mark the JIRA as fixed in the not-yet-released 2.1.2. However, it is all too easy to choose 2.1.x instead of 2.1.2. The problem is that 2.1.x JIRAs won't show up in reports we generate for release notes for 2.1.2.

Any objections?


Joe

I'd like to remove the *.x versions from our JIRA project so that people will be encouraged to include the specific version as the fix version. I'll work through the JIRAs and cleanup references prior to removal (I have to do this anyway for 2.1.2).

smime.p7s
Description: S/MIME Cryptographic Signature