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 3A7BFD720 for ; Wed, 27 Jun 2012 09:30:33 +0000 (UTC) Received: (qmail 92631 invoked by uid 500); 27 Jun 2012 09:30:32 -0000 Delivered-To: apmail-incubator-ooo-dev-archive@incubator.apache.org Received: (qmail 92438 invoked by uid 500); 27 Jun 2012 09:30:32 -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 92430 invoked by uid 99); 27 Jun 2012 09:30:32 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Jun 2012 09:30:32 +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.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; Wed, 27 Jun 2012 09:30:27 +0000 Received: by bkcjm2 with SMTP id jm2so675134bkc.6 for ; Wed, 27 Jun 2012 02:30:05 -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 :content-type:content-transfer-encoding; bh=7NoRm8O6ecElD0d9F6LSIOeZnECDn00avBOXcwAh8us=; b=YI8+fPSUuzjK2hBUMfKCS8To6veX0m6qIifIMnse9+5Fq7mCRS9d/CvOw6gZplImhC jYrFyk2xLFKL/+s3Hf3KYBY7h2Cw2nH5XZehICl5tjPcaclYZTLDQev3zvoqgdtTM00Q eHyVbTZqgMhmys5Kk0giQ1q6TRQjinh5zSRUq4PMnQUAVSRMv5sqsR7bdjS1KO2PgEGu vTgGv5NFzIYrAwVEq0PKNKErjWlTl07h0KlHnywFNjzIfbJqXwOCYnrtR9nMtM8VPcUq 6xGkCY9HLvTT8awWBRhITmxku+ULQlKJ5VqAq4VGUyOtReFPEf+rkeojAHwKubqJ/U38 IH1Q== Received: by 10.204.148.83 with SMTP id o19mr6713334bkv.96.1340789405641; Wed, 27 Jun 2012 02:30:05 -0700 (PDT) Received: from [9.155.131.111] (deibp9eh1--blueice2n2.emea.ibm.com. [195.212.29.172]) by mx.google.com with ESMTPS id fw10sm54027409bkc.11.2012.06.27.02.30.03 (version=SSLv3 cipher=OTHER); Wed, 27 Jun 2012 02:30:04 -0700 (PDT) Message-ID: <4FEAD29A.9050300@googlemail.com> Date: Wed, 27 Jun 2012 11:30:02 +0200 From: Oliver-Rainer Wittmann User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1 MIME-Version: 1.0 To: ooo-dev@incubator.apache.org Subject: [UPDATE SERVICE] proposal to activate the update service for OOo 3.2 and OOo 3.2.1 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi, I am sorry - again some stuff regarding our update service. As it has been pointed out in [1] there are some more OOo versions out there for which we can activate the update service. Thus, I am proposing to activate the update service for installed OOo 3.2 and OOo 3.2.1 instances for which we have an AOO 3.4 installation package. These would be OOo 3.2/3.2.1 versions of the following languages on Windows, MacOS X, Linux 32bit and Linux 64bit: - English (US) - Arabic - Chinese (simplified) - Chinese (traditional) - Czech - Dutch - French - Galician - German - Hungarian - Italian - Japanese - Portuguese (Brazilian) - Russian - Spanish If nobody objects, I will work on the following tasks to make this happen: (A) get in contact with Apache infrastructure in order to get the following Update URLs of OOo 3.2.1 and OOo 3.2 redirected: -- http://update35.services.openoffice.org/ProductUpdateService/check.Update -- http://update34.services.openoffice.org/ProductUpdateService/check.Update These are the Update URL of OOo 3.2.1 resp. OOo 3.2 (B) creation of corresponding XML documents at the following URLs: -- http://www.openoffice.org/projects/update35/ProductUpdateService/check.Update -- http://www.openoffice.org/projects/update34/ProductUpdateService/check.Update The content of these XML documents will be more or less the same as for our OOo 3.3 update service, found at [2], but will contain download URLs with corresponding URL parameters in order to identify the OOo version which is using the update function. [1] http://markmail.org/message/kepaycvdsaibijn6 [2] http://www.openoffice.org/projects/update36/ProductUpdateService/check.Update Best regards, Oliver.