Hi all, I thought I could spend a few words to describe the current status of our efforts towards Syncope 3.0.
Starting point is [1] where the overall code reorganization - now completed - and the new components are introduced. Also relevant is [2] which describes the identified issues in JIRA for the new major version. Overall, this is the state by component: * Core is completed with several enhancements and improvements * Console was upgraded to latest components and technologies but is still lacking the features to manage WA (Keymaster and SRA management was done, instead) * Enduser was rewritten from scratch to uniform with Console as much as possible but needs work to finalize and possibly include new features derived from WA as auth profile management or SAML2 / OIDC account linking * SRA is completed * Keymaster is completed and provided in two flavors: self, e.g. REST and internal storage based, and zookeeper, requiring an Apache Zookeeper deployment * WA, based on Apereo CAS 6.4, is mostly completed but under continuous refinement * Documentation is the sore point, essentially stuck at the same content as 2.1 Similarly as we've done at the time of Syncope 2.0, I believe it is the case to publish some RCs before the official 3.0.0. I don't think, however, we are yet a the point of issuing RC1, as we'd need at least to: 1. update the Documentations at least with main changes 2. bring the Enduser application at a degree of usability 3. introduce at least some WA configuration items for Console WDYT? Regards. [1] https://cwiki.apache.org/confluence/display/SYNCOPE/%5BDISCUSS%5D+Syncope+3.0 [2] https://issues.apache.org/jira/projects/SYNCOPE/versions/12322510 -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
