+1 makes sense to me. Colm.
On Thu, Nov 28, 2013 at 1:17 PM, Francesco Chicchiriccò <[email protected] > wrote: > Hi all, > while the release of maintenance version 1.1.5 is ongoing, I am realizing > that the set additions currently scheduled for 1.2.0 [1] is probably too > large. > > A consistent number of new things has already been implemented in 1.2.0 > (mainly related to RESTful cleanup + various upgrades and enhancements) > and, if you take a look at what is missing [2], you will see some sparse > items, including the most noticeable SYNCOPE-119 (Realm-based > authorization) which actually hides a large set of activities. > > This made me think that 1.2.0 will be ready for Q1 2013, i.e. almost a > year after 1.1.0 - which is probably too long. > > Other considerations: > * SYNCOPE-300 (and SYNCOPE-349 by consequence) could fit better in 1.2.0 > due to its REST characteristics > * 1.2.0 currently depends on CXF 3.0.0 and LOG4J2 snapshots > * SYNCOPE-152 depends on Directory's eSCIMo - which still has to get its > first release > > Hence my proposal: > 1. move SYNCOPE-300 and SYNCOPE-349 to 1.2.0 > 2. create new release "1.3.0 Virtuoso" > 3. move SYNCOPE-119 to 1.3.0 > 4. keep working on 1.2.0 until CXF and LOG4J2 publish their stable > releases, then move any residual issue from 1.2.0 to 1.3.0. > > WDYT? > > [1] https://cwiki.apache.org/confluence/display/SYNCOPE/ > Roadmap#Roadmap-1.2.0%28Intermezzo%29 > [2] https://issues.apache.org/jira/issues/?jql=project+%3D+ > SYNCOPE+AND+fixVersion+%3D+%221.2.0%22+AND+status+%3D+ > Open+ORDER+BY+priority+DESC > > -- > Francesco Chicchiriccò > > Tirasa - Open Source Excellence > http://www.tirasa.net/ > > ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member > http://people.apache.org/~ilgrosso/ > > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
