Unlock opensaml-parent ?

[Tom Zeller]

>> but pending that I guess I’ll leave opensaml-parent locked. But it seems like we should unlock it for the upcoming release, in general.
> 
> 
> I think of the parent POMs like another kind of dependency.  We're *allowed* to rev it for a minor release, but I don't think there's anything which says we *must*.  Like other dependencies I think we rev it when we have a reason to rev it.  Not necessarily just because there's a newer/shinier one out there.
> 
> Having said that, since it's been awhile since 3.1.0, offhand I imagine there are things in parent TRUNK-SNAPSHOT that we need.  And certainly we should sync up opensaml and the IdP to use the same parent for the 3.2.0 release.

I remember talking about this on a dev call, but I don’t remember the details. For an IdP release, should all of the projects in our stack have the same parent version ? i.e. should we unlock OpenSAML and java-support and spring-extensions ? They might be unlocked already at the moment, but I’m asking more in general. If so, then it seems that whenever we unlock the IdP we should unlock upstream projects too.