Return-Path: X-Original-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3A6E5DF70 for ; Sun, 26 Aug 2012 19:52:18 +0000 (UTC) Received: (qmail 18560 invoked by uid 500); 26 Aug 2012 19:52:17 -0000 Delivered-To: apmail-incubator-ooo-dev-archive@incubator.apache.org Received: (qmail 18483 invoked by uid 500); 26 Aug 2012 19:52:17 -0000 Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ooo-dev@incubator.apache.org Delivered-To: mailing list ooo-dev@incubator.apache.org Received: (qmail 18475 invoked by uid 99); 26 Aug 2012 19:52:17 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 26 Aug 2012 19:52:17 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of fcassia@gmail.com designates 209.85.210.175 as permitted sender) Received: from [209.85.210.175] (HELO mail-iy0-f175.google.com) (209.85.210.175) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 26 Aug 2012 19:52:10 +0000 Received: by iaky10 with SMTP id y10so6920258iak.6 for ; Sun, 26 Aug 2012 12:51:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=Poj+EqZPn59dzOu4/OeKC+ZXlF70QrY3hbtxZ7e6k8M=; b=wtwwz5pmUECOWUNA0U2JJcyOsOuLjZDubYZfv4gQ4NutdzYSvVlIuy691wMBtKR+yl GK1RyvNThzJE8G/XAmpYZmD2nuUTgc6m6MrzMF3JTox1rTHp819BLRapBoobS02hAK1p 58S5nXKvcC+5qK60bZ9YinlSeg4y74YtBmxJ4SJ+UTmF2Tv5OnVL+9jUzrID5cdKSryi /VhpXIUjtWpvrrswM+seNU1OMvreR+GqysPOfQSVRrxLQvS8SPM+jja1PhFhoXOMcoPu 4+YFaIMhg5jCBl2J33HXVwR4PfgHxfuN3Q+cu5m9B0EB83KQmzh7En43+G7n8GCBZD8d 6Elw== MIME-Version: 1.0 Received: by 10.50.95.231 with SMTP id dn7mr8165492igb.36.1346010709472; Sun, 26 Aug 2012 12:51:49 -0700 (PDT) Received: by 10.231.117.222 with HTTP; Sun, 26 Aug 2012 12:51:49 -0700 (PDT) Date: Sun, 26 Aug 2012 16:51:49 -0300 Message-ID: Subject: AOO "long-term support" ? From: Fernando Cassia To: ooo-dev@incubator.apache.org Content-Type: multipart/alternative; boundary=e89a8f2354bf33b6cc04c8308a9d --e89a8f2354bf33b6cc04c8308a9d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi, I wonder if the =C2=B4new management=C2=B4 at AOO ;) has any plans with reg= ards to =C2=B4long term support=C2=B4 for AOO?. I mean... it=C2=B4d be nice if we knew in advance that AOO 3.4.x will be supported (bugfixes-stability and security issues if any) for the next =C2= =B4x=C2=B4 years. Or just how long each version is supported (say, if an AOO 4.0 is released, for how long AOO 3.4x will continue having security fixes, etc). Not that I have any worries or needs on the particular... I was just thinking about Ubuntu=C2=B4s "LTS" releases scheme and the thought crossed = my mind if AOO project leaders had something like that in mind, or the talk of release lifetime was ever thojught or even discussed... So, I=C2=B4m all ears. ;) FC --=20 During times of Universal Deceit, telling the truth becomes a revolutionary act - George Orwell --e89a8f2354bf33b6cc04c8308a9d--