We won't be reviewing or accepting PRs to anything but master and maybe
1.9.x. We just don't have the cycles to maintain older versions. We
strive to maintain backward compatibility whenever possible. WE try to
make keycloak upgradable and will make fixes around this accordingly.
We have said this from day one. Releases are tagged, so if you need to
stay on a specific version for whatever reason, then you can branch and
maintain the branch yourselves. I don't recommend this though as you
will get no help from us and you'll be on your own. If stability is
something you strive for, then I suggest you work off the community
version our product is based on: 1.9.x.
On 9/9/16 8:24 AM, Juraci Paixão Kröhling wrote:
On 09/09/2016 02:17 PM, Stian Thorgersen wrote:
> With a new minor release of Keycloak every 6 weeks that ends up being a
> lot of dead branches to keep around. Removing them makes it clear they
> are no longer maintained and stops people from sending PRs to them (this
> regularly happens).
How about adding a CONTRIBUTING.md , telling people to send PRs only to
the branches you'd review/accept? If there's a CONTRIBUTING.md file,
GitHub will add a link to it on the "Submit PR" page.
- Juca.
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev