[cle-release-team] KNL fixVersions fixed
Neal Caidin
neal.caidin at apereo.org
Mon Mar 10 03:38:03 PDT 2014
see below. Hopefully addresses all the concerns.
Thanks,
Neal
> Sam Ottenhoff <mailto:ottenhoff at longsight.com>
> March 7, 2014 at 2:36 PM
>
>
>>
> 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.
AFAICT released and unreleased versions both show up as available
versions for affects versions and fix versions. Only archived versions
are hidden.
>
>> 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've archived 10.0 [Tentative].
>
>>
>> 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.
>
> Inline image 1
I think I've fixed this. Learning curve.
>
>
>> 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
> Neal Caidin <mailto:neal.caidin at apereo.org>
> March 7, 2014 at 2:24 PM
> Thanks. Responses below.
>
>> Sam Ottenhoff <mailto:ottenhoff at longsight.com>
>> March 7, 2014 at 12:17 PM
>> I'm seeing anomalies.
>>
>> https://jira.sakaiproject.org/browse/KNL#selectedTab=com.atlassian.jira.plugin.system.project%3Aversions-panel
>>
>> I see 10.0-qa03 but no versions for qa01, qa02.
> 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.
>> Shouldn't there be a qa04 version for the branch merger to use? The
>> SAK version has a qa04 version, so KNL, SAM, POLLS, PRFL all need the
>> same version.
> Yes, I agree. All Sakai projects should have a q04 version. When qa04
> is released then I need to add a qa05 version to all Sakai projects. I
> was sure that I added qa04 to KNL. Indeed it was not there when I just
> looked, so I re-added it. The other Sakai projects look like they do
> have qa04 already, as expected.
>
>>
>> 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?
>>
>> 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?
>>
>> Sakai 2.9 uses Kernel 1.3.
>>
>> Sakai 2.8 uses Kernel 1.2.
> Yes, I know. I frequently refer to the POMs to make sure that I get
> this right.
>>
>> So these are redundant.
> They would be, yes, but I don't see them.
>> 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.
>
>>
>>
>> On Fri, Feb 28, 2014 at 8:38 AM, Neal Caidin <neal.caidin at apereo.org
>> <mailto:neal.caidin at apereo.org>> wrote:
>> >
>> > KNL fixVersions for Sakai 10 now reflect qa01 through qa04
>> >
>> > At this point there are not any fixVersions of 10.0-qa04. All the fixes
>> > after February 22, 2014 seem to have had a fix version of 11
>> > [Tentative], so those did not get updated.
>> >
>> > If you see any anomalies please let me know.
>> >
>> > Thanks,
>> > Neal
>> >
>> >
>> > --
>> > Neal Caidin
>> > Sakai Community Coordinator
>> > Apereo Foundation
>> > neal.caidin at apereo.org <mailto:neal.caidin at apereo.org>
>> > Skype me! (but let me know in advance for the first interaction) -
>> nealkdin
>> >
>> > _______________________________________________
>> > cle-release-team mailing list
>> > cle-release-team at collab.sakaiproject.org
>> <mailto:cle-release-team at collab.sakaiproject.org>
>> > http://collab.sakaiproject.org/mailman/listinfo/cle-release-team
>> Neal Caidin <mailto:neal.caidin at apereo.org>
>> February 28, 2014 at 8:38 AM
>> KNL fixVersions for Sakai 10 now reflect qa01 through qa04
>>
>> At this point there are not any fixVersions of 10.0-qa04. All the
>> fixes after February 22, 2014 seem to have had a fix version of 11
>> [Tentative], so those did not get updated.
>>
>> If you see any anomalies please let me know.
>>
>> Thanks,
>> Neal
>>
>>
>
> Sam Ottenhoff <mailto:ottenhoff at longsight.com>
> March 7, 2014 at 12:17 PM
> I'm seeing anomalies.
>
> https://jira.sakaiproject.org/browse/KNL#selectedTab=com.atlassian.jira.plugin.system.project%3Aversions-panel
>
> I see 10.0-qa03 but no versions for qa01, qa02. Shouldn't there be a
> qa04 version for the branch merger to use? The SAK version has a qa04
> version, so KNL, SAM, POLLS, PRFL all need the same version.
>
> I thought we didn't want a version of "10.0 [tentative]" without a
> specific tag.
>
> I now see merge versions for 10, 2.9, 2.8, 1.3, and 1.2. Argh!!!
>
> Sakai 2.9 uses Kernel 1.3.
>
> Sakai 2.8 uses Kernel 1.2.
>
> So these are redundant. I assume someone added 2.9 and 2.8 merge
> versions recently. These should be deleted.
>
>
> On Fri, Feb 28, 2014 at 8:38 AM, Neal Caidin <neal.caidin at apereo.org
> <mailto:neal.caidin at apereo.org>> wrote:
> >
> > KNL fixVersions for Sakai 10 now reflect qa01 through qa04
> >
> > At this point there are not any fixVersions of 10.0-qa04. All the fixes
> > after February 22, 2014 seem to have had a fix version of 11
> > [Tentative], so those did not get updated.
> >
> > If you see any anomalies please let me know.
> >
> > Thanks,
> > Neal
> >
> >
> > --
> > Neal Caidin
> > Sakai Community Coordinator
> > Apereo Foundation
> > neal.caidin at apereo.org <mailto:neal.caidin at apereo.org>
> > Skype me! (but let me know in advance for the first interaction) -
> nealkdin
> >
> > _______________________________________________
> > cle-release-team mailing list
> > cle-release-team at collab.sakaiproject.org
> <mailto:cle-release-team at collab.sakaiproject.org>
> > http://collab.sakaiproject.org/mailman/listinfo/cle-release-team
> Neal Caidin <mailto:neal.caidin at apereo.org>
> February 28, 2014 at 8:38 AM
> KNL fixVersions for Sakai 10 now reflect qa01 through qa04
>
> At this point there are not any fixVersions of 10.0-qa04. All the
> fixes after February 22, 2014 seem to have had a fix version of 11
> [Tentative], so those did not get updated.
>
> If you see any anomalies please let me know.
>
> Thanks,
> Neal
>
>
--
Neal Caidin
Sakai Community Coordinator
Apereo Foundation
neal.caidin at apereo.org
Skype me! (but let me know in advance for the first interaction) - nealkdin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/cle-release-team/attachments/20140310/b0c35f70/attachment-0001.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: postbox-contact.jpg
Type: image/jpeg
Size: 1265 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/cle-release-team/attachments/20140310/b0c35f70/attachment-0002.jpg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 16294 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/cle-release-team/attachments/20140310/b0c35f70/attachment-0001.png
-------------- next part --------------
A non-text attachment was scrubbed...
Name: compose-unknown-contact.jpg
Type: image/jpeg
Size: 770 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/cle-release-team/attachments/20140310/b0c35f70/attachment-0003.jpg
More information about the cle-release-team
mailing list