Shibboleth Developers

[Peter Schober <>]

Playing a little with jira I noticed a few minor things and asked
Scott about one of those.

* Scott Cantor 
<>
 [2008-10-09 03:02]:
> > said filter in jira also contains "resolved" issues:
> > https://bugs.internet2.edu/jira/secure/IssueNavigator.jspa?requestId=10014
> > since you're the author of this filter, would you care to exclude
> > those if you have a few minutes to spare?
> 
> No, Jira actually separates resolved from closed issues. The filter
> includes everything I haven't closed, which means anything that
> hasn't been fixed in shipping code.
> 
> That's important because:
> 
> - I can do a final pass when I ship to make sure I've tested all the fixes.
> - People can see what's been fixed but not released.

Thanks, I noticed the difference (resolved/closed) but for some reason
had the impression of this not being used or at least not being used
consistently across the components. Now I see I should have asked this
on-list in the first place.

* Scott's shared filter "Shibboleth 2.0 SP Open Issues" includes
  resolved issues. Now I know "open" means "not part of any release".

* Both of Chad's shared filters "OpenSAML 2 Open Issues" as well as
  "Shibboleth 2 Open Issues" don't include any closed or resolved
  issues.

Note that all sets are called "Open Issues", so neither the meaning
of "open" not "resolved" nor "closed" seems to be shared across the
C++/Java devide -- there's a single 'resolved' issue on the java side,
with plenty of recently 'closed' issues (i.e. which are certainly not
part of any release).
I understand that the people involved have different ways doing things
(which is perfectly fine and I think has served the project well) and
I can certainly roll my own filters. I was just confused because of
the different ways the same flags seem to be used.

Cheers,
-peter

-- 

 - vienna university computer center
Universitaetsstrasse 7, A-1010 Wien, Austria/Europe
Tel. +43-1-4277-14155, Fax. +43-1-4277-9140