[cle-release-team] Adding Fix Versions

[Matthew Jones]

Everything that's in trunk, that's a bug, potentially should be QA tested,
so it can be verified and merged. Most likely though these are just going
to be blocker and critical issues.

Though probably only need to focus on the ones that have the 10.x merge
flag already set too, by a developer or someone from the release team.

So that's going to be a much smaller group than even this filter is.


On Tue, Feb 25, 2014 at 12:28 PM, Neal Caidin <neal.caidin at apereo.org>wrote:

> Thanks!
>
> I get the fix version process.
>
> The filter still doesn't make sense to me. We need a filter that shows
> what needs to be QA tested in order to be merged into the Sakai 10 branch.
> I think that is a different problem than your filter solves?
>
> -- Neal
>
>   Matthew Jones <matthew at longsight.com>
>  February 25, 2014 at 12:24 PM
> Everything thing prior to the cut off last week would be in QA03 release.
>
> For QA04 only the branch manager who actually does the merge should be
> setting this fix version. Everything else that gets merged into trunk would
> only have a fix version of 11.0 [tentative] set by the developer that
> commits to trunk.
>
> Anything else would be a anticipated fix version which we agreed we aren't
> doing.
>
> Essentially I *think* the filter for issues to be QA'd that aren't yet in
> 10 that you're probably looking for is below
>
> "Issues with a fix version of 11, but not a fix version of 10 that are a
> bug and are fixed but not yet verified either.". Probably something similar
> but separate for kernel?
>
> project = "SAK" AND fixVersion not in versionMatches("10.*") and
> fixVersion in versionMatches("11.*") and type="Bug" and Resolution =
> "Fixed" and Status != "Verified"
>
>
>
>
>   Neal Caidin <neal.caidin at apereo.org>
>  February 25, 2014 at 11:22 AM
> I feel like a broken record, perhaps one that was mis-recorded in the
> studio and needs a new digital master recording. ;-)
>
> When I notice issues that are resolved and clearly are targeted for the QA
> branch, if they don't have a fix version, I'm putting in QA04. That way the
> will show up in this filter for QA testers:
>
> https://jira.sakaiproject.org/browse/SAK-24415?filter=13763
>
> I think we should try for getting all the blocker and critical items QA
> tested (currently a little less than 50 issues). There are over 750 issues
> total, and I don't see how QA can get this number tested. For Sakai 11,
> maybe we can set up a different process (e.g. be more proactive on getting
> Sakai 11 issues tested closer to when they are fixed).
>
> Cheers,
> 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/20140225/de0cdbda/attachment-0001.html 
-------------- 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/20140225/de0cdbda/attachment-0001.jpg