[keycloak-dev] Guaranteed Backwards Compatibility

[Stian Thorgersen]

The aim is to always be backwards compatible, and deprecate rather than
remove.

Non-public APIs are not covered. For example only user storage SPI is a
public API, while other SPIs like event listener is private and as such we
reserve the right to break it.

On Tue, 11 Jun 2019 at 06:01, Justin Gross <jgross.biz at gmail.com> wrote:

> Marek Posolda brought up a good point in another thread about certain
> pieces of Keycloak being guaranteed to have backward compatibility. Is
> there a guideline for this, a strict outline of what is guaranteed to
> continue being backwards compatible or any documentation outlining what
> should be kept strictly compatible during a version change?
>
> TLDR;
>
> I recognize and understand the semantic versioning (or at least presume
> to) however I ask this so that I can make sure I consider the list of
> sacred things (if there is one) and especially take this into account while
> I design/propose/work on anything within the Keycloak project. I tried
> Google searching but only found the upgrade docs at
> keycloak.org/docs/latest/upgrading.
>
>
> Thank you,
>
> Justin Gross
> _______________________________________________
> keycloak-dev mailing list
> keycloak-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/keycloak-dev
>