[cle-release-team] KNL fixVersions fixed

[Sam Ottenhoff]

>  This is intentional if you mean that you cannot set affects version or
> fix version to qa01 or qa02. I archived the versions for qa01 and qa02
> specifically so that they cannot be assigned to affects version or fix
> version. I thought that was our Sakai core team decision? I can easily
> unarchive either one temporarily so that issues can be adjusted, if
> necessary, but I think that should only be temporary if needed on a
> particular issue or two.
>


I don't know, I thought we were just releasing these versions which means
they don't show up as available versions when a user enters a new JIRA.  By
archiving them, we have no ability to correct a JIRA and indicate that it
affects qa01 and was fixed in qa02.  But I don't have firm feelings on
this.  It's not as important as these other items below.



> I thought we didn't want a version of "10.0 [tentative]" without a
> specific tag.
>
> Yes, I agree. No issues should have "10.0 [tentative]" as a fix version.
> There are Resolved issues that have "10.0 [tentative]" as an affects
> version, but only resolved issues. There should not be any unresolved
> issues (resolution = unresolved) using "10.0 [tentative]" for the affects
> version. I assumed that since they are resolved and we have a fix version,
> that the affects version really doesn't matter any more. I think it will be
> flipped to affects version of 10.0 when we release?
>
>

Yes, when we release, we can consolidate all of these precise versions into
one big 10.0 version.  But I'd rather users not have the choice of
10.0[Tentative] as it's not a version we want anyone to use.  Let's just
remove it until we need it.



>
> I now see merge versions for 10, 2.9, 2.8, 1.3, and 1.2.  Argh!!!
>
> I don't see this for KNL.  And I don't see merge versions for 2.9 and 2.8
> in KNL. I looked both in the versions administrative area and in the search
> box. What are the steps you use to see these versions?
>


Go to a KNL issue and edit.

[image: Inline image 1]



 I assume someone added 2.9 and 2.8 merge versions recently.  These should
> be deleted.
>
> This brings up a question. I believe different people are maybe adding and
> deleting versions to help out, which is cool. The problem is
> accountability. Personally I think I should be accountable. But if I am to
> be accountable, I need to be the point person for all the version changes.
> By point person, I mean that if others make changes, they should check with
> me first, and mostly, I probably should be making the changes.
>


Yes, you are the point person.  Let's get a system and consistency in
place.

Everyone else please do not edit versions for the core projects.  Please
post to this list if you have issues.

--Sam
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/cle-release-team/attachments/20140307/699f7a8f/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: knl.PNG
Type: image/png
Size: 16592 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/cle-release-team/attachments/20140307/699f7a8f/attachment-0001.png