Hello,
I think it would have been helpful to announce that on the keycloak-user
/-dev mailing-lists and Keycloak blog.
(In case it was announced - it was IMHO not stressed enough).
Some folks (including me) based their internal forks of Keycloak on top of
a "maintenance branch" like 2.1.x
expecting to be able to channel compatible fixes / patches into the said
custom fork.
With those maintenance branches now gone - this model no longer works.
Given that keycloak has now over 500 forks I guess that I'm not the only
one who followed that model.
I would suggest to keep some maintenace branches for previous versions
(e.g. 2.1.x) around to enable users
to upgrade their forks in a timely manner.
Cheers,
Thomas
2016-09-09 11:34 GMT+02:00 Stian Thorgersen <sthorger(a)redhat.com>:
They where deleted on purpose. 2.2 is about to be released, which
means
there won't be any more 2.1 or 2.0 releases so these branches are no longer
needed.
On 9 September 2016 at 10:55, Thomas Darimont <thomas.darimont@googlemail.
com> wrote:
> Hello,
>
> just found out that some of the maintenance branches: 2.1.x, 2.0.x are no
> longer available in in the the keycloak github repository.
>
> Only the 1.9.x & master branches are left :(
>
> Did someone accidentally remove those branches?
>
> Cheers,
> Thomas
>
> _______________________________________________
> keycloak-dev mailing list
> keycloak-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/keycloak-dev
>