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 D1EDF9FFA for ; Tue, 22 May 2012 06:26:26 +0000 (UTC) Received: (qmail 88855 invoked by uid 500); 22 May 2012 06:26:26 -0000 Delivered-To: apmail-incubator-ooo-dev-archive@incubator.apache.org Received: (qmail 88704 invoked by uid 500); 22 May 2012 06:26:26 -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 88681 invoked by uid 99); 22 May 2012 06:26:25 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 May 2012 06:26:25 +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 (nike.apache.org: domain of orwittmann@googlemail.com designates 209.85.214.47 as permitted sender) Received: from [209.85.214.47] (HELO mail-bk0-f47.google.com) (209.85.214.47) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 May 2012 06:26:17 +0000 Received: by bkcjm2 with SMTP id jm2so4918218bkc.6 for ; Mon, 21 May 2012 23:25:57 -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=UKk6qnmd5fHfWBCJm3E5k66UPPwYremiQPMnm41QaZk=; b=RWrhdOA1pqMGQD954LYD0xPUexWEW/3vw49eKZkqAJ0eRk/G7XmIQMlyDcvCm9VeCq xM/p/ANTbGrYCCX+0boHnPUML53QXc5VCsyHo3ZZfvPvbUyxjeJj8mzjNzejmXjavj7v YbgjFMhVH3GA1Q9rlssNxzPVBmwbJo7TvL2SEz+hx4XZpmPs/hd6pW/M8H6aeDSPFOTK 2vziE3bwixusz8/PXszcsPY82JQ8LKrCIdLr8yTPNbNBi3sJmDaAbUP7YLlNMaJaIzFK TdK3m6SpXZiCwAKujESsSbrvBKMh9uE9ZP5/xprt75185HRg0djxigLhcrqHiqvx9Jxm BE8Q== Received: by 10.204.153.21 with SMTP id i21mr8397745bkw.38.1337667957365; Mon, 21 May 2012 23:25:57 -0700 (PDT) Received: from [9.155.131.111] (deibp9eh1--blueice2n2.emea.ibm.com. [195.212.29.172]) by mx.google.com with ESMTPS id n19sm30087570bkv.14.2012.05.21.23.25.55 (version=SSLv3 cipher=OTHER); Mon, 21 May 2012 23:25:56 -0700 (PDT) Message-ID: <4FBB3175.8020507@googlemail.com> Date: Tue, 22 May 2012 08:25:57 +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: [UPDATE SERVICE] proposal for a AOO 3.4 update service References: <4FB247E8.3020507@googlemail.com> <4FB2A466.1030100@googlemail.com> <4FB34B1F.3030105@googlemail.com> <4FB3F651.2060300@googlemail.com> <4FB3FD19.8040703@googlemail.com> <4FBA2A49.8050303@googlemail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi On 21.05.2012 18:20, Roberto Galoppini wrote: >> >> [snip] >> >>>> >>>> I'd keep it simple. >>>> >>>> Two main tasks: >>>> >>>> 1) Identify whether there is an update available for the user's current >>>> install >>>> >>>> 2) Direct the user to that update >>>> >>>> I'd keep #2 really really simple. We already know there is an update. >>>> We already have logic on http://download.openoffice.org for finding >>>> the correct download. So for #2 just always send the user to >>>> http://download.openoffice.org. >>>> >>>> That approach even does magical things. For example, in the future, >>>> the user might be running OpenOffice on a 64-bit Windows, but they are >>>> running 32-bit OO, since that is all that exists. But when we come >>>> out with a new 64-bit of AOO 3.x, the logic on >>>> http://download.openoffice.org will automatically suggest it. Ditto >>>> for better language support. Someone might be running Spanish AOO 3.4 >>>> but then decide to upgrade to Catalan AOO 3.X (assuming it is >>>> available). >>>> >>> >>> Is this what we plan to do for OOo 3.3 users too? >>> >> >> For OOo 3.3 I have made an own proposal - please have a look at thread >> "[UPDATE SERVICE] proposal a OOo 3.3 update service" >> >> > > Thanks Olivier, > > I'm trying to catch up with that thread too, are you working on > making it via the AOO download page or direct downloads? > Currently, this is open - both is possible. For Linux installations is would be a little bit complicated, if we decide to go for a "static" solution. But more will follow today on the other thread. Best regards, Oliver.