Shibboleth Developers

["Scott Cantor" <>]

Not taking a position on this particular suggestion, but I wanted to note
that we're engaged in a fairly deep discussion right now amongst the team on
getting ourselves committed to a more rigorous policy on the svn
organization and how we address version numbers.

As part of that discussion, I'm definitely ending my haphazardness about
adding features to the branches, meaning that any new features, especially
involving configuration, will have to go into a new minor revision.

In other words, if I added this feature, it isn't going to show up
until/unless a 1.4 or 2.1 SP is released, and that has significant support
implications because I don't have enough help maintaining this code to
support that many branches at once.

So don't ask for something unless you also accept the consequences, which
might include an accelerated time frame for dropping support of an older
version. Granted, most of the time these new minor releases should be drop
in compatible, so the upgrade will be painless, but it's still something to
consider.

-- Scott