Re: JIRA versions 2.0.x 2.1.x
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. BTW - Shouldn't the Fix Version field remain blank until someone either starts working on the issue or code is integrated into svn? -Donald Joe Bohn wrote: 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. 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). Any objections? Joe smime.p7s Description: S/MIME Cryptographic Signature
Re: JIRA versions 2.0.x 2.1.x
Donald Woods wrote: 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. BTW - Shouldn't the Fix Version field remain blank until someone either starts working on the issue or code is integrated into svn? I think there are different opinions on the Fix Version field. We've been using it in the past to target fixes for a particular release before a JIRA is resolved. I guess my opinion would be to leave it blank until there is some reason to mark for a perspective release. When the issue is eventually resolved it should be updated to reflect the actual version(s) that will include the fix once released. Joe -Donald Joe Bohn wrote: 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. 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). Any objections? Joe
JIRA versions 2.0.x 2.1.x
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. 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). Any objections? Joe
Re: JIRA versions 2.0.x 2.1.x
+1 for removal of the *.x versions. Jarek On Wed, Jul 23, 2008 at 10:43 AM, Joe Bohn [EMAIL PROTECTED] wrote: 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. 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). Any objections? Joe
Re: JIRA versions 2.0.x 2.1.x
+1. I think we should do this in Geronimo Eclipse Plug-in (GEP) too. On Wed, Jul 23, 2008 at 8:13 PM, Joe Bohn [EMAIL PROTECTED] wrote: 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. 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). Any objections? Joe -- Thanks, Shiva
