Shibboleth Developers

[Walter Hoehn <>]

One risk in having too many categories is that users might have trouble 
 grokking the categorization when they enter bugs.  This might lead to 
greater initial misrouting of bugs, which might cause extra work for some.

Right now, the following versions/milestones are setup:

Shibboleth
Versions - alpha-1, alpha-2, alpha-2.5
Milestones - beta-1, beta-2

OpenSAML
Versions - beta-1, beta-1.5
Milestones - beta-2

Thoughts?

-Walter




 wrote:
> is there any value in decomposing Origin and Target any further?
>
> For instance, on the origin side, the HS is relatively simple and won't 
> see  continual  enhancement. The AA, on the other hand, is likely to 
> continue  to evolve, over some longish period. However, I can see an  
> argument being made both ways.
>
> On the target side, I can imagine  the RM becoming a separate component.
>
> On the other hand, we're all aware of the pitfalls of starting out and 
> dividing things too finely.
>
> Once we agree on the components, what's the next step?
>
>     - specifying versions and targets? How do we  want to use these?

--
-------------------------
Walter F. Hoehn, Jr
Systems Programmer
Columbia University - EPIC
-------------------------

Attachment: pgpsm6veoM_Av.pgp
Description: PGP signature