Re: [keycloak-dev] next release should be 2.5 not 2.4.1
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(a)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(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev