[cle-release-team] JIRA Version Maintenance

[Beth Kirschner]

Hi Neal,

   Comments below...

- Beth

On Nov 27, 2012, at 2:27 PM, Neal Caidin wrote:

> Summary
> --------------------
> Done, mostly.  All 2.9.0 alpha, beta, and rc versions merged into 2.9.0 and some cleanup per Matt's cleanup list (see below).
> 
> 
> Notes
> ---------------
>             * Side affect of merge is that there are over 800 issues for which at least one affectedVersion is 2.9.0 and at least one fixVersion is 2.9.0. Query : affectedVersion = "2.9.0" and fixVersion = "2.9.0"
>             * Only affected SAK, SAM, and KNL . 
>             * wrt Resolved/Open/Awaiting issues having fix version unset,I may check with the Samigo team because they may be using the fixVersion in a slightly different way than the CLE release team overall. 
>              
> Questions
> -----------------
>             * I don't see a way to bulk change the fixVersion in Jira. For those Jira admins out there, am I missing something? Many fields showed, but not fixVersion.
If you delete a version, JIRA will offer you the option to bulk change all open JIRAs with an affectedVersion or fixVersion set to the soon to be deleted version. You're given the option of changing the version or leaving it blank. These are two separate questions, so you can change the affectedVersion to 2.9.0, and change the fixedVersion to nothing (which is what I'd suggest).

>             * Is it preferable to have an empty fixVersion or "2.10 [tentative]" ?  There are some issues that I'm hoping we will get into 2.9.2, and setting to "2.10 [tentative]" fix version seems wrong. On the other hand, we are only setting the fixVersion for the version in which the Jira is actually fixed, but maybe "2.10 [tentative] is a good place holder?
> 
I think it's preferable to have an empty fixVersion -- we generally don't fill in that field until it's actually fixed. That makes querying easier, and it's also one less thing to change (and change again) as releases move forward.

> Thanks,
> 
> 
> Neal Caidin
> 
> Sakai CLE Community Coordinator
> nealcaidin at sakaifoundation.org
> Skype: nealkdin
> AIM: ncaidin at aol.com
> 
> 
> 
> 
> 
> On Nov 19, 2012, at 4:15 PM, Matthew Jones <matthew at longsight.com> wrote:
> 
>> I'm good with this.
>> 
>> Cleaning up the intermediary tags was also something I kept up on in the past:
>> 
>> - All Verified or Resolved issues that *were* merged should be closed
>> - All Resolved issues that were not merged (often because they weren't verified) should either be moved to the next release or have the fix version unset
>> - All Open or Awaiting review issues should either have the fix version unset or moved to the next version
>> 
>> Essentially the final release should just be all closed issues, so this is a decent amount of cleanup effort.
>> 
>> 
>> 
>> On Mon, Nov 19, 2012 at 4:04 PM, Beth Kirschner <bkirschn at umich.edu> wrote:
>> Hi Neal,
>> 
>>    One thing that Anthony has done in the past, following a release, was to remove all the JIRA alpha, beta & release-candidate tags, and consolidate them into one 2.9.0 release. When you delete a version in JIRA, it offers you the option to change the deleted version to another version (e.g. 2.9.0). I think we should continue doing this so that the version list is less cluttered. Let me know if you'd like some off-line help on how to do this. Does anyone else think we should _not_ continue with this practice?
>> 
>> - Beth
>> _______________________________________________
>> cle-release-team mailing list
>> cle-release-team at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/cle-release-team
>> 
> 
> _______________________________________________
> cle-release-team mailing list
> cle-release-team at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/cle-release-team