[keycloak-dev] distribution of adapters

[Stian Thorgersen]

My concerns with releasing all adapters simultaneously as the server are:

* We need to release all adapters, even those that haven't changed
* Users will believe they have to update all their applications, even those where the adapter has no changes

I believe we should have separate repo, documentation and examples for adapters. However, I have no issue with grouping related adapters into one (for example all Java adapters in one repo). Reasoning behind this is that there are different build tools, expected documentation formats, example formats, etc. depending on the programming language.

We already have Java, NodeJS, JavaScript and Jenkins adapters. They are all released differently (Java in Maven, JS in Bower, NodeJS in god knows where!) so we already have an overhead of doing releases, IMO having independent releases would actually simplify things. 

With regards to users I believe it's a pretty demanding requirement to expect a user to upgrade the server and all applications in one go. They may not even have control over this, for example one company provides the KC server, while another provides applications. We need to make sure there is backwards compatibility with adapters and that they can be updated independently and also it should be clear what a user is expected to upgrade when. 

----- Original Message -----
> From: "Bill Burke" <bburke at redhat.com>
> To: keycloak-dev at lists.jboss.org
> Sent: Thursday, February 19, 2015 6:03:56 PM
> Subject: [keycloak-dev] distribution of adapters
> 
> I think there is a different here between community and product.
> 
> In community:
> * Adapters should each have a separate download.  This has a side effect
> of showing us which adapters are popular (not to mention increasing our
> download numers ;)
> * All adapters are released simultaneously with a server release
> * Adapters can have individual patch releases.
> * If we want to release a patched adapter, use a micro version scheme.
> First 3 numbers correspond to the keycloak version the adapter was built
> against.  Last number is the patch number of the adapter:
> 
> We release Keycloak 1.1.0:
> - keycloak-jetty-1.1.0.0
> Werelease a patch of jetty adapter for keycloak 1.1.0
> - keycloak-jetty-1.1.0.1
> 
> I'm not sure how all that effects product and git branches.  Ideally
> you'd have matching branches for major keycloak server release for the
> adapter.
> 
> i.e.
> 
> Keycloak_server_branch_1.1.x
> Keycloak_adapters_branch_1.1.x
> 
> 
> --
> Bill Burke
> JBoss, a division of Red Hat
> http://bill.burkecentral.com
> _______________________________________________
> keycloak-dev mailing list
> keycloak-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/keycloak-dev
>