Hi all,
having received a whole positive feedback, I am going to create a new
1_2_X branch from trunk.
Regards.
On 03/07/2014 14:47, Francesco Chicchiriccò wrote:
HI all,
I am resurrecting this old thread because almost all issues for 1.2.0
have been resolved
https://issues.apache.org/jira
Il 03/07/2014 14:47, Francesco Chicchiriccò wrote:
HI all,
I am resurrecting this old thread because almost all issues for 1.2.0
have been resolved
https://issues.apache.org/jira/browse/SYNCOPE/fixforversion/12322505/?selectedTab=com.atlassian.jira.jira-projects-plugin:version-issues-panel
Il giorno 03/lug/2014, alle ore 14:47, Francesco Chicchiriccò
ha scritto:
> HI all,
> I am resurrecting this old thread because almost all issues for 1.2.0 have
> been resolved
>
> https://issues.apache.org/jira/browse/SYNCOPE/fixforversion/12322505/?selectedTab=com.atlassian.jira.jira-projec
On 07/03/2014 02:47 PM, Francesco Chicchiriccò wrote:
HI all,
I am resurrecting this old thread because almost all issues for 1.2.0
have been resolved
https://issues.apache.org/jira/browse/SYNCOPE/fixforversion/12322505/?selectedTab=com.atlassian.jira.jira-projects-plugin:version-issues-panel
+1.
Colm.
On Thu, Jul 3, 2014 at 1:50 PM, Fabio Martelli
wrote:
> Il 03/07/2014 14:47, Francesco Chicchiriccò ha scritto:
>
> HI all,
>> I am resurrecting this old thread because almost all issues for 1.2.0
>> have been resolved
>>
>> https://issues.apache.org/jira/browse/SYNCOPE/fixforversio
Il 03/07/2014 14:47, Francesco Chicchiriccò ha scritto:
HI all,
I am resurrecting this old thread because almost all issues for 1.2.0
have been resolved
https://issues.apache.org/jira/browse/SYNCOPE/fixforversion/12322505/?selectedTab=com.atlassian.jira.jira-projects-plugin:version-issues-pane
HI all,
I am resurrecting this old thread because almost all issues for 1.2.0
have been resolved
https://issues.apache.org/jira/browse/SYNCOPE/fixforversion/12322505/?selectedTab=com.atlassian.jira.jira-projects-plugin:version-issues-panel
I am proposing to enter in a "feature-freeze" phase fo
Il 20/02/2014 08:45, Francesco Chicchiriccò ha scritto:
Hello there,
lately CXF and LOG4J2 published their updated milestone releases
(3.0.0-milestone2 and 2.0-rc1 respectively), hence our current trunk
(1.2.0-SNAPSHOT) does not depend from SNAPSHOT releases any more
(well, at least for the mo
Sure, it makes sense.
Colm.
On Thu, Feb 20, 2014 at 8:35 AM, Massimiliano Perrone <
massimiliano.perr...@tirasa.net> wrote:
> On 02/20/2014 08:45 AM, Francesco Chicchiriccň wrote:
>
>> Hello there,
>> lately CXF and LOG4J2 published their updated milestone releases
>> (3.0.0-milestone2 and 2.0-
On 02/20/2014 08:45 AM, Francesco Chicchiriccò wrote:
Hello there,
lately CXF and LOG4J2 published their updated milestone releases
(3.0.0-milestone2 and 2.0-rc1 respectively), hence our current trunk
(1.2.0-SNAPSHOT) does not depend from SNAPSHOT releases any more
(well, at least for the mome
Il 20/02/2014 08:45, Francesco Chicchiriccò ha scritto:
Hello there,
lately CXF and LOG4J2 published their updated milestone releases
(3.0.0-milestone2 and 2.0-rc1 respectively), hence our current trunk
(1.2.0-SNAPSHOT) does not depend from SNAPSHOT releases any more
(well, at least for the mo
Hello there,
lately CXF and LOG4J2 published their updated milestone releases
(3.0.0-milestone2 and 2.0-rc1 respectively), hence our current trunk
(1.2.0-SNAPSHOT) does not depend from SNAPSHOT releases any more (well,
at least for the moment).
As I was writing below, there is plenty of stuff
12 matches
Mail list logo
