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

[Neal Caidin]

That sounds reasonable to me. 

Honestly anything that is decided is fine by me. My main concern is that we be consistent and that the documentation reflect the decision. 

If I am understanding the documentation correctly, I think it aligns with what Steve is saying, in which case we would not need to create beta and rc versions in Jira. This might also dovetail into the other discussion (Versioning Jira Components) to simplify things and have less release tasks. 

WDYT?

-- Neal

P.S. I might still use labels to keep track of some things, but that should not affect the process or cause extra work for anybody.


On Mar 19, 2013, at 4:05 AM, Steve Swinsburg <steve.swinsburg at gmail.com> wrote:

> You would set 2.9.2 tentative as the affects version. If it was fixed quickly its fix version would probably be 2.9.2 tentative as well. But that is fine IMO as it represents what happened. If it didn't get fixed in time for 2.9.2 then its version would automatically switch to affects 2.9.2 and could be fixed in 2.9.3. 
> 
> I also think that beta and rc versions in Jira are a bit of overkill, just use the next tentative. If you want a report on issues fixed, run it based on dates between last tag and now. 
> 
> Cheers
> Steve
> 
> Sent from my iPhone
> 
> On 19/03/2013, at 1:30, Neal Caidin <nealcaidin at sakaifoundation.org> 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