[cle-release-team] Jira filter for issues merged into 2.9.2

[Noah Botimer]

I see absolutely no problem with having an upcoming release version set for Affects and Fix in this case. It is accurate and clear: at some point, the hypothetical issue affects only the upcoming release, and at some later point, it no longer does. So long as Affects is always less than or equal to Fix, we're good to go.

Granted, these should be relatively rare, but they do happen on the order of a handful of things each release. One obvious example is a task to track work/testing on any conversion scripts.

Thanks,
-Noah

On Mar 18, 2013, at 10:30 AM, Neal Caidin wrote:

> https://confluence.sakaiproject.org/display/MGT/Sakai+Jira+Guidelines
> 
> According to the Jira guidelines, under the Resolution section: Update Fix Version to the next major release version, do not use alpha or beta releases (e.g. use 2.8.2, 2.9, 2.10 : do NOT use 2.9b07, 2.9a1, trunk)
> 
> 
> For the other topic affects version, under the Version section, it says "The Affects Version should be set to the released version of the instance of Sakai being used. Do not use unreleased versions."   . The problem I have with this, which happens in real life, is say a bug is introduced in 2.9.2-rc01, but does not exist in 2.9.1 . I surely do not want to use 2.9.1, the release version, as the affects version, when it is not. I want to use 2.9.2-rc01 and get that fixed as a regression before going on to 2.9.2-rc02. How do I designate this in the Jira? 
> 
> -- Neal
> 
> 
> 
> On Mar 18, 2013, at 9:35 AM, Aaron Zeckoski <azeckoski at unicon.net> wrote:
> 
>> Just to play devil's advocate...
>> 
>> Is there a reason to not just use the 2.9.2 [Tentative] version until
>> we release it? It seems like maybe just extra trouble to have beta and
>> rc versions floating around (and more confusing when people are trying
>> to set the affects/fix versions).
>> 
>> Surely anything that affects or is fixed in 2.9.2 tentative would be
>> part of whatever upcoming release right (though maybe we care to know
>> if it was part of the previous rc/beta tag)?
>> 
>> -AZ
>> 
>> 
>> On Mon, Mar 18, 2013 at 9:31 AM, Sam Ottenhoff <ottenhoff at longsight.com> wrote:
>>> 
>>>> 
>>>> I'm wondering if we should standardize on using the "[Tentative]" version
>>>> as the fix version, and only use the alpha, beta, and release candidate as
>>>> affects version?
>>> 
>>> 
>>> The tentative versions (unreleased versions) should not be used for Affects
>>> Version unless it is a bug only against trunk.
>>> 
>>> The Fix Version should be the next version to be released.  Right now, that
>>> should be 2.9.2-rc01.  I would recommend a bulk update to move anything with
>>> Fix Version of 2.9.2 to 2.9.2-rc01.
>>> 
>>> --Sam
>>> 
>>> _______________________________________________
>>> cle-release-team mailing list
>>> cle-release-team at collab.sakaiproject.org
>>> http://collab.sakaiproject.org/mailman/listinfo/cle-release-team
>>> 
>> 
>> 
>> 
>> -- 
>> Aaron Zeckoski - Software Architect - http://tinyurl.com/azprofile
>> _______________________________________________
>> 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