Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 3D499200D15 for ; Thu, 5 Oct 2017 18:02:05 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 3A3461609E1; Thu, 5 Oct 2017 16:02:05 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 8139C1609DA for ; Thu, 5 Oct 2017 18:02:04 +0200 (CEST) Received: (qmail 56263 invoked by uid 500); 5 Oct 2017 16:02:03 -0000 Mailing-List: contact dev-help@syncope.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@syncope.apache.org Delivered-To: mailing list dev@syncope.apache.org Received: (qmail 56252 invoked by uid 99); 5 Oct 2017 16:02:03 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Oct 2017 16:02:03 +0000 Received: from mail-pg0-f45.google.com (mail-pg0-f45.google.com [74.125.83.45]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 60B921A040E for ; Thu, 5 Oct 2017 16:02:03 +0000 (UTC) Received: by mail-pg0-f45.google.com with SMTP id s184so6812479pgc.0 for ; Thu, 05 Oct 2017 09:02:03 -0700 (PDT) X-Gm-Message-State: AHPjjUgJIOrt6lInuMLf6sVwqkGAm/7N7KNL0eFTStfv7Z0k6+CeDMym 85SD8sCVhYroeLntj+D4rXJ62GCUep2Mxweh5qw= X-Google-Smtp-Source: AOwi7QCGwDqL6lNyYFDMLkaBESxqQ4W/fSRSJWHKwzjddUkYFGAKaVRpy5arABXsmlnOsk/KGfhawMXq7FWxE5nftos= X-Received: by 10.98.198.139 with SMTP id x11mr23843119pfk.101.1507219323065; Thu, 05 Oct 2017 09:02:03 -0700 (PDT) MIME-Version: 1.0 Reply-To: coheigea@apache.org Received: by 10.100.165.105 with HTTP; Thu, 5 Oct 2017 09:02:02 -0700 (PDT) In-Reply-To: <09602363-6b2e-949d-c375-2af91675caba@tirasa.net> References: <09602363-6b2e-949d-c375-2af91675caba@tirasa.net> From: Colm O hEigeartaigh Date: Thu, 5 Oct 2017 17:02:02 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [DISCUSS] Time for 2.0.6? To: "dev@syncope.apache.org" Content-Type: multipart/alternative; boundary="94eb2c0a4e64599ced055aced845" archived-at: Thu, 05 Oct 2017 16:02:05 -0000 --94eb2c0a4e64599ced055aced845 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable +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=C3=B2 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 available. >> >> From the other side, instead, several bugs have been already fixed [2], >> some of them quite relevant. >> >> What about releasing 2.0.6 anytime soon? I don't see many reasons to wai= t >> for more. >> >> Regards. >> >> [1] https://issues.apache.org/jira/issues/?jql=3DstatusCategory% >> 20=3D%20new%20AND%20project%20=3D%2012313120%20AND%20fixVersion% >> 20=3D%2012341555%20ORDER%20BY%20priority%20DESC,%20key%20ASC >> [2] https://issues.apache.org/jira/issues/?jql=3DstatusCategory% >> 20=3D%20done%20AND%20project%20=3D%2012313120%20AND% >> 20fixVersion%20=3D%2012341555%20ORDER%20BY%20priority%20DESC,%20key%20AS= C >> >> > --=20 Colm O hEigeartaigh Talend Community Coder http://coders.talend.com --94eb2c0a4e64599ced055aced845--