[keycloak-dev] thoughts on 1.2->1.3 releases

[Stian Thorgersen]

----- Original Message -----
> From: "Bill Burke" <bburke at redhat.com>
> To: "Stian Thorgersen" <stian at redhat.com>
> Cc: keycloak-dev at lists.jboss.org
> Sent: Tuesday, 7 April, 2015 3:06:30 PM
> Subject: Re: [keycloak-dev] thoughts on 1.2->1.3 releases
> 
> Do we need a Keycloak SAML client adapter?

Not for 1.2 AFAIK, but we'll need it for 1.3

> 
> On 4/7/2015 8:41 AM, Stian Thorgersen wrote:
> > Makes sense, we have a limited amount of time for 1.2 though. Maybe we'll
> > need to do a 1.3 feature release, then focus on refactoring for 1.4?
> >
> > For 1.2 here's my list for features:
> >
> > Yes, please
> >
> > * Unify app and clients (KEYCLOAK-1187 Stian)
> > * Persist client grants (KEYCLOAK-1070 Marek)
> > * View/manage client grants in account management (KEYCLOAK-1070 Marek)
> > * View available clients in account management (KEYCLOAK-1070 Marek)
> > * Remove PL dependencies - SAML (KEYCLOAK-1006 Bill)
> > * Remove PL dependencies - LDAP (KEYCLOAK-1007 Marek)
> > * Identity brokering mapping (KEYCLOAK-1097 Bill)
> > * Identity brokering - improve token store and retrieval (KEYCLOAK-992)
> >
> > If time
> >
> > * Introduce KeycloakContext (KEYCLOAK-1109 Stian)
> > * Dynamic client registration (KEYCLOAK-684)
> > * Auth SPI (KEYCLOAK-369)
> > * Required actions SPI - related to Auth SPI, maybe even same SPI?!?
> > (KEYCLOAK-1188)
> > * OpenID Certification - ongoing (KEYCLOAK-524)
> > * LDAP enhancements (KEYCLOAK-886)
> > * PatternFly/RCUE enhancements (KEYCLOAK-887 Stian)
> >
> >
> > ----- Original Message -----
> >> From: "Bill Burke" <bburke at redhat.com>
> >> To: keycloak-dev at lists.jboss.org
> >> Sent: Tuesday, 7 April, 2015 2:22:18 PM
> >> Subject: [keycloak-dev] thoughts on 1.2->1.3 releases
> >>
> >> I was thinking that we would cram as many features we can into the 1.2
> >> release, then for 1.3 really focus on:
> >>
> >> * refactoring the SPIs
> >> * refactoring the UIs.  Reorganizing them, consolidating them, thinking
> >> of good defaults.  Think about any features we can remove to simplify
> >> things
> >> * Break out the Public and Private apis
> >> * Talk about "config profiles", i.e. Default application templates, and
> >> stuff like that.
> >> * Improving the "Hello World" experience.
> >>
> >> Really focus on usability, simplification, documentation, examples, etc.
> >>    Take a step back and really think about how to make Keycloak easier to
> >> use and consume.
> >>
> >> --
> >> 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
> >>
> 
> --
> Bill Burke
> JBoss, a division of Red Hat
> http://bill.burkecentral.com
>