[sakai2-tcc] [cle-release-team] 292triage label ?

[Noah Botimer]

I've heard rumor of some mega-filters that have the right stuff, but I can never seem to find or create them. Is this to do with botched sharing settings? The JIRA gurus should surely be able to share what they have crafted, and I see little advantage in denying the less-than-gurus the ability to make their filters public if there is a way to mark and list the "official" ones.

Maybe a silly question, but is there a way to compose filters as by a set union? Two layers (one to get it right for a given project, and one to aggregate filters by ID) might be a way to encapsulate some of the complexity if such a thing is possible.

Thanks,
-Noah

On Feb 25, 2013, at 5:20 PM, Steve Swinsburg wrote:

> If there is a way to create a cross project filter that collects all issues that need merging based on their appropriate merge status flags, ie 1.5.x in profile2, 1.3.x in kernel et al, then I would much prefer that. Issues will then drop off the filter as they are merged. 
> I don't use the labels because they do the same as the merge status flag
> 
> 
> Gesendent von meinem iPhone
> 
> On 26/02/2013, at 8:26, "May, Megan Marie" <mmmay at indiana.edu> wrote:
> 
>> Wouldn't this be complicating a semi-complicated work flow?      And creating data redundancy?   
>> 
>> Megan
>> 
>> 
>> -----Original Message-----
>> From: cle-release-team-bounces at collab.sakaiproject.org [mailto:cle-release-team-bounces at collab.sakaiproject.org] On Behalf Of Neal Caidin
>> Sent: Monday, February 25, 2013 3:53 PM
>> To: cle-release-team at collab.sakaiproject.org; sakai2-tcc at collab.sakaiproject.org 2
>> Subject: [cle-release-team] 292triage label ?
>> 
>> Hi All,
>> 
>> At least for my purposes, I found it useful to use the 291triage label for the CLE 2.9.1 release. Part of the reason for this is that different indies have different versions. CLE, Kernel and Samigo are fairly straightforward, but then we also have Basic LTI, Lessons, Polls, Search, MSGCNTR, Profile2, etc which are not picked up by searching on the 1.3.x or 2.9.x merge flags.  Having a label means I can guarantee my filter picks up things I want, for communication to QA and others, that a more complex query might miss.
>> 
>> Any concerns with me continuing to use labels? I think in general, if folks don't tag SAK, KNL, and Samigo issues with the labels, I can use our "standard" filters to bulk apply the label(s) so as not to miss anything. So I don't think there is much of a downside.
>> 
>> The reason I ask, versus just doing, is because I want to put out a call to the prod, dev and qa lists for people to start tagging issues for 2.9.2 , and if there are major objections to this, I want to know before making that call.
>> 
>> Thanks,
>> Neal
>> 
>> _______________________________________________
>> 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
> _______________________________________________
> sakai2-tcc mailing list
> sakai2-tcc at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc