Re: [DISCUSS] Time for 2.0.6?

2017-10-05 Thread Colm O hEigeartaigh
+1. Colm. On Thu, Oct 5, 2017 at 1:28 PM, Lorenzo Di Cola wrote: > +1. > > Regards, > > Lorenzo Di Cola > > > Il 05/10/2017 08:38, Francesco Chicchiriccò ha scritto: > >> Hi all, >> it seems that Syncope 2.0.6 is at a point where the issues left [1] are >> either new

[jira] [Resolved] (SYNCOPE-1186) Remove copy of SAMLSSOResponseValidator and SSOValidatorResponse when CXF 3.1.13 is out

2017-10-05 Thread Colm O hEigeartaigh (JIRA)
[ https://issues.apache.org/jira/browse/SYNCOPE-1186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved SYNCOPE-1186. -- Resolution: Fixed > Remove copy of SAMLSSOResponseValidator and

[jira] [Commented] (SYNCOPE-1186) Remove copy of SAMLSSOResponseValidator and SSOValidatorResponse when CXF 3.1.13 is out

2017-10-05 Thread ASF subversion and git services (JIRA)
[ https://issues.apache.org/jira/browse/SYNCOPE-1186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16193086#comment-16193086 ] ASF subversion and git services commented on SYNCOPE-1186: -- Commit

Re: [DISCUSS] Time for 2.0.6?

2017-10-05 Thread Lorenzo Di Cola
+1. Regards, Lorenzo Di Cola Il 05/10/2017 08:38, Francesco Chicchiriccò ha scritto: Hi all, it seems that Syncope 2.0.6 is at a point where the issues left [1] are either new features that can be safely moved to 2.0.7 (or 2.0.8, or even 2.1.0) or minor issues which seem not to have an

Re: [DISCUSS] Time for 2.0.6?

2017-10-05 Thread Massimiliano Perrone
Il 05/10/2017 08:38, Francesco Chicchiriccò ha scritto: Hi all, it seems that Syncope 2.0.6 is at a point where the issues left [1] are either new features that can be safely moved to 2.0.7 (or 2.0.8, or even 2.1.0) or minor issues which seem not to have an easy or effective fix immediately

Re: [DISCUSS] Time for 2.0.6?

2017-10-05 Thread Marco Di Sabatino Di Diodoro
Il 05/10/2017 08:38, Francesco Chicchiriccò ha scritto: Hi all, it seems that Syncope 2.0.6 is at a point where the issues left [1] are either new features that can be safely moved to 2.0.7 (or 2.0.8, or even 2.1.0) or minor issues which seem not to have an easy or effective fix immediately

Re: [DISCUSS] Time for 2.0.6?

2017-10-05 Thread Matteo Alessandroni
+1 for me! Regards, Matteo Alessandroni On 05/10/2017 08:38, Francesco Chicchiriccò wrote: Hi all, it seems that Syncope 2.0.6 is at a point where the issues left [1] are either new features that can be safely moved to 2.0.7 (or 2.0.8, or even 2.1.0) or minor issues which seem not to have

Re: [DISCUSS] Time for 2.0.6?

2017-10-05 Thread Matteo Di Carlo
Actually most of them are new features, so I agree. Matteo On 05/10/2017 09:06, Fabio Martelli wrote: Il 05/10/2017 08:38, Francesco Chicchiriccò ha scritto: Hi all, it seems that Syncope 2.0.6 is at a point where the issues left [1] are either new features that can be safely moved to 2.0.7

Re: [DISCUSS] Time for 2.0.6?

2017-10-05 Thread Andrea Patricelli
+1 also for me. Best regards, Andrea Il 05/10/2017 08:38, Francesco Chicchiriccò ha scritto: Hi all, it seems that Syncope 2.0.6 is at a point where the issues left [1] are either new features that can be safely moved to 2.0.7 (or 2.0.8, or even 2.1.0) or minor issues which seem not to have

Re: [DISCUSS] Time for 2.0.6?

2017-10-05 Thread Fabio Martelli
Il 05/10/2017 08:38, Francesco Chicchiriccò ha scritto: Hi all, it seems that Syncope 2.0.6 is at a point where the issues left [1] are either new features that can be safely moved to 2.0.7 (or 2.0.8, or even 2.1.0) or minor issues which seem not to have an easy or effective fix immediately

[DISCUSS] Time for 2.0.6?

2017-10-05 Thread Francesco Chicchiriccò
Hi all, it seems that Syncope 2.0.6 is at a point where the issues left [1] are either new features that can be safely moved to 2.0.7 (or 2.0.8, or even 2.1.0) or minor issues which seem not to have an easy or effective fix immediately available. From the other side, instead, several bugs