[keycloak-dev] next release should be 2.5 not 2.4.1
Stian Thorgersen
sthorger at redhat.com
Thu Nov 24 05:10:24 EST 2016
Just saw the other threads that it's already removed. We could either
recover them and mark them deprecated or remove and do a 2.5 release.
Whatever you think is best.
On 24 November 2016 at 11:07, Stian Thorgersen <sthorger at redhat.com> wrote:
> Actually thinking about this some more. Why don't we just keep the old
> user federation SPI in for now and mark them as deprecated. Then we can
> remove in 3.0.0C.CR1 release instead? Makes more sense to remove in a major
> update rather than a minor update. That would also give you more time on
> figuring out the migration issue?
>
> On 23 November 2016 at 21:22, Bill Burke <bburke at redhat.com> wrote:
>
>> Next community release should be 2.5 not 2.4.1. Since we are removing
>> support for the User Federation SPI, this will break backward
>> campatibility with 2.4.0.Final. Point releases should not break
>> backward compatibility so, IMO, the next community release should be
>> 2.5.0, not 2.4.1.
>>
>> Bill
>>
>> _______________________________________________
>> keycloak-dev mailing list
>> keycloak-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/keycloak-dev
>>
>
>
More information about the keycloak-dev
mailing list