Versions post 3.1.0 release ?

[Daniel Fisher]

On Wed, Mar 11, 2015 at 10:02 AM, Rod Widdowson <rdw at steadingsoftware.com>
wrote:

> It looks like 3.2 is weeks away, are we really saying that if we have to do
> a 3.1.1 release we'll be saying "here is a security release, it also
> contains a whole bunch of bug fixes that you may or may not want"?  If not
> what will we be saying?  That should provide guidance as what sort of bug
> fixes we would put in.
>
> I'm not saying that this doing any of this is a necessarily bad idea, I'm
> saying that we (I really) need to understand upfront what the expected
> behaviors will be.
>

I lean towards a pragmatic approach as well. I would only create a 3.1.x
branch if your trunk version had moved on to 3.2.0 and you needed a patch
release before you could cut the 3.2.0 release.

My impression is the branch early model worked well for large groups with
lots of external patches. But there may be benefits I'm not thinking of.

--Daniel Fisher
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/dev/attachments/20150311/aeac412d/attachment-0001.html