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 4436897A4 for ; Mon, 4 Jun 2012 09:29:58 +0000 (UTC) Received: (qmail 65169 invoked by uid 500); 4 Jun 2012 09:29:58 -0000 Delivered-To: apmail-incubator-ooo-dev-archive@incubator.apache.org Received: (qmail 64790 invoked by uid 500); 4 Jun 2012 09:29:57 -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 64768 invoked by uid 99); 4 Jun 2012 09:29:56 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Jun 2012 09:29:56 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of orwittmann@googlemail.com designates 209.85.215.175 as permitted sender) Received: from [209.85.215.175] (HELO mail-ey0-f175.google.com) (209.85.215.175) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Jun 2012 09:29:50 +0000 Received: by eaal1 with SMTP id l1so1083564eaa.6 for ; Mon, 04 Jun 2012 02:29:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=YptDV/SGQbdQVOtN0c+wY0/p5iZabJoOeT/TBEEbLro=; b=HfBoLaXO9jYjsPwPaHb/WD263rx93kz/1n1JIBiHT4+D2v7uPv31EQ22a9wZ4rawhe pK4ewsAfCGDZ9i6L0iPeXavhLImLXV/CHGwstjJ51o3+/UGmvdYRJUI1RtujYVr1/w4W kD7k2clc8zIIZW9b5K/xVBRGngdlypVlJ7XPcRtLTW86bb6L+WlA4sY+C4NTxVWGXe3s ShHcJI8txWmIDFsERGfq/t96IOHSNOlZETTMnzPhUqQtH+NGYRMAiwggV+TQQ9NkJ9Tc HZ3MoLETROXmrh8T+/3ly3z9BqMxb6jMd7GZTypahwJGKp/PLTPBKM8s7sZygmmMawX/ G/YA== Received: by 10.14.47.144 with SMTP id t16mr4597697eeb.172.1338802169341; Mon, 04 Jun 2012 02:29:29 -0700 (PDT) Received: from [9.155.131.111] (deibp9eh1--blueice3n2.emea.ibm.com. [195.212.29.180]) by mx.google.com with ESMTPS id c51sm35093702eei.12.2012.06.04.02.29.27 (version=SSLv3 cipher=OTHER); Mon, 04 Jun 2012 02:29:28 -0700 (PDT) Message-ID: <4FCC8000.8000305@googlemail.com> Date: Mon, 04 Jun 2012 11:29:36 +0200 From: Oliver-Rainer Wittmann User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1 MIME-Version: 1.0 To: ooo-dev@incubator.apache.org Subject: Re: [HEADS UP] Re: [UPDATE SERVICE] proposal a OOo 3.3 update service References: <4FB38E67.7040406@googlemail.com> <4FBB92F2.4090500@googlemail.com> <4FC5F9EB.10102@googlemail.com> <4FC72E03.2010206@googlemail.com> <4FC88A35.90901@googlemail.com> <4FCC6B81.9030207@googlemail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi, On 04.06.2012 10:11, Roberto Galoppini wrote: > On Mon, Jun 4, 2012 at 10:02 AM, Oliver-Rainer Wittmann > wrote: >> Hi, >> >> >> On 02.06.2012 18:21, Kay Schenk wrote: >>> >>> On Fri, Jun 1, 2012 at 2:24 AM, Oliver-Rainer Wittmann< >>> orwittmann@googlemail.com> wrote: >>> >>>> [snip] >>>> >>>> >>>> One other question: does this take care of OOo 3.2 upgrades as well? >>>>> >>>>> >>>> >>>> Not yet planned nor tested, but I assume that the XML document only needs >>>> minor adjustments. >>>> OOo 3.2 has the UpdateURL >>>> http://update34.services.**openoffice.org/. >>>> .. >>>> OOo 3.2.1 has the Update URL >>>> http://update35.services.**openoffice.org/. >>>> .. >>>> >>>> But once the update service is working for OOo 3.3, we can easily do the >>>> same for OOo 3.2 and OOo 3.2.1 (and even former versions). >>> >>> >>> >>> Oliver, don't go any further back than maybe 3.1. The 3.0 update URL is >>> the one that uses POST instead of GET, and creates mayhem! >>> >>> This is update30.... >>> >>> DO NOT redirect this one. I don't know about some of the others. >>> >>> We should probably be fie with update34, update 35. >>> >> >> My personal opinion is that an update service for OOo 3.3, OOo 3.2.1 and OOo >> 3.2 is enough to reach our user base. May be also for OOo 3.1.1 and OOo 3.1, >> if we see a high number of users on OOo 3.2.1 and OOo 3.2. >> >>> >>> Everything else seems great! >>> >>> >> >> Thanks. >> Let see what happens, when we start tomorrow with the "Italian OOo 3.3 >> update service". > > Tomorrow at which time? > If nobody objects and nothing unforeseen happened I would like to start tomorrow European morning at 10:00 (GMT+2). FYI, I have to check with ASF infrastructure team, if the redirect will be available at this time. Best regards, Oliver.