I'd like to reopen KEYCLOAK-311 as IMO it's not solved. This is not referring to
the claim mapping work you've done, it's something else.
Before we can do a release we need to make sure that database migration works (I know they
don't atm as social providers and social links are lost). We also need to add
transformation of JSON exports and representations so older versions can be imported into
1.2.0.Beta1.
With all the changes we've done for this release (modules, claim mapping, identity
brokering, oidc endpoints, ...) we need to do more testing this time around!
----- Original Message -----
From: "Bill Burke" <bburke(a)redhat.com>
To: keycloak-dev(a)lists.jboss.org
Sent: Wednesday, 11 March, 2015 8:06:04 PM
Subject: [keycloak-dev] 1.2.beta1 planning, need you to defer things
I'd like to do 1.2.beta1 by end of month or earlier. Please go through
the jira list and defer things you are not going to get to in the next
1-2 weeks. Thanks.
Done
I'm going to try and close existing bugs and implement features needed
for
jboss.org guys over the next 2 weeks as well as test out master to
make sure things still work.
With regards to
jboss.org guys we shouldn't just add features because they request it.
Take for example KEYCLOAK-1045, which was easily solved with we already have. Another one
is KEYCLOAK-1051, which I think is a horrible idea.
Bill
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev