Shibboleth Developers

[Tom Scavo <>]

On 4/29/05, Walter Hoehn 
<>
 wrote:
> If you mean frozen for the 1.x line, then that sounds reasonable,
> especially since any release before 2.0 will probably be a 1.3.x
> release. 

Sounds reasonable.

> During the move to 2.0, any number of components might have
> to change, but of course we want to try and be sensitive to which
> changes might break these kinds of dependencies and avoid those when
> possible. 

Thanks.

> API stability is mostly dictated by usage requirements,
> though.  Just because something is labeled as a java interface,
> however, doesn't mean that you can count on it staying the same
> forever.

Perhaps, but an orderly, phased out obsolescence is preferable to an
out-and-out modification of the API.  In other words, formally
deprecate any legacy components for a predictable period of time
preceding their disappearance.  This is especially important going
forward since shib, gridshib, lionshare, etc. are developing
more-or-less along separate paths.  We would like some guarantees (or
at least some advanced warnings) with respect to API stability.

Thanks,
Tom