Create 3.2 Branch

[Cantor, Scott]

On 12/10/15, 5:40 AM, "dev on behalf of Rod Widdowson" <dev-bounces at shibboleth.net on behalf of rdw at steadingsoftware.com> wrote:



>There are a few bugs, currently fixed against 3.2.1 which would need to be merged
>forward.  Or of course we could just start the at 3.2 branch at r8019 (or
>wherever).

Oh, you mean to mark where the actual 3.3 changes start? It will basically be the revision prior to updating the POM.

>But there is a meta discussion (which I may have missed/forgotten) whether
>the next release we "expect" to ship is 3.3  or 3.2.1. If we expect that
>3.2.1 will only be for critical security fixes then we won’t be merging
>anything, just fixing the bug.  If we expect to do a roll-up 3.2.1 prior to
>a 3.3 then it's another matter.  I have enough nitty little bugs which
>require a minor upgrade that I'd favour the former, and from the language
>above it seems that you do too,

It's fairly hard to predict. Anything could come up that warrants a patch. So far the biggest one is probably Chris' issue with the old connector that I failed to account for, but I'm not sure it warrants an emergency fix at this stage. Stored IDs are not a widely used feature.

-- Scott