Hi team,now that keycloak-beta4 was released, we have an updated PR from abstractj to use that version ([1]), combined w/ an upcoming release of our parent (to leverage the kc-beta4 JARs), see [2].At the moment we have a few open PRs:Please review, but DO NOT merge them! Why? The KC PR goes in first, afterwards I will merge the other items, based on review feedback.By tomorrow that all should be done (read: merged) and there will be a staged repo for tests (and openshift updates), watch out for the email!
As mentioned on IRC, the nominees for the testing, are:* sblanc, cvasilak, dbevenius, lholmquist, lfryc and abstractj
Besides testing the UPS staging repo, please test our quickstarts (including their client SDKs) as well:(use the master branch - there will be a .Beta2 TAG, if all goes well there)Last but not least, please 'test' the documentation as well. For instance the new UPS guide:or other items of the new 'UPS doc center' :-)Hopefully, by Wednesday we have an awesome 1.0.0.Beta2 and shortly after that we can go to CODE_FREEZE for the 1.0.0.FinalAny thoughts ?-MatthiasPS: others, besides the nominated folks, are welcome to test the things as well :)-Matthias
On Fri, Aug 1, 2014 at 6:35 AM, Matthias Wessendorf <matzew@apache.org> wrote:--Hi team,
based on [1] I thought about our release timelines until 1.0.0.Final, and shortly after.
1.0.0.Beta2: 07/Aug/14
This needs to include Keycloak-beta4, and might slip by one day, but not much more of a delay.
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf