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 895859931 for ; Mon, 27 Feb 2012 10:13:32 +0000 (UTC) Received: (qmail 76089 invoked by uid 500); 27 Feb 2012 10:13:32 -0000 Delivered-To: apmail-incubator-ooo-dev-archive@incubator.apache.org Received: (qmail 76017 invoked by uid 500); 27 Feb 2012 10:13: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 76008 invoked by uid 99); 27 Feb 2012 10:13:32 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Feb 2012 10:13: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 (nike.apache.org: domain of jogischmidt@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; Mon, 27 Feb 2012 10:13:24 +0000 Received: by bkcjg15 with SMTP id jg15so1043856bkc.6 for ; Mon, 27 Feb 2012 02:13:04 -0800 (PST) Received-SPF: pass (google.com: domain of jogischmidt@googlemail.com designates 10.205.121.138 as permitted sender) client-ip=10.205.121.138; Authentication-Results: mr.google.com; spf=pass (google.com: domain of jogischmidt@googlemail.com designates 10.205.121.138 as permitted sender) smtp.mail=jogischmidt@googlemail.com; dkim=pass header.i=jogischmidt@googlemail.com Received: from mr.google.com ([10.205.121.138]) by 10.205.121.138 with SMTP id gc10mr5621494bkc.23.1330337584511 (num_hops = 1); Mon, 27 Feb 2012 02:13:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=FdDVKalU8k/Wdo47I8cczCMSIhK8PWuo6o0AVb2Foow=; b=LiYtTcoft39MqLFs7Dqz+xOwtzrwSrQS0lTLi2Y2ffGBLBTCXDo7OUR6XEOkq5vEip 0o9eqkweqjDOmvm8VuWf5ppBPgioAhQrpcfCt8A0zft3d5zIyNA+HxBJgddOcF3pUedH UxTvP0IIQNEf1DB9z+U/VHaUauipyw5OF6g58= Received: by 10.205.121.138 with SMTP id gc10mr4538258bkc.23.1330337584453; Mon, 27 Feb 2012 02:13:04 -0800 (PST) Received: from [9.155.131.20] (deibp9eh1--blueice4n2.emea.ibm.com. [195.212.29.188]) by mx.google.com with ESMTPS id bw9sm23753212bkb.8.2012.02.27.02.13.03 (version=SSLv3 cipher=OTHER); Mon, 27 Feb 2012 02:13:03 -0800 (PST) Message-ID: <4F4B572E.9020109@googlemail.com> Date: Mon, 27 Feb 2012 11:13:02 +0100 From: =?UTF-8?B?SsO8cmdlbiBTY2htaWR0?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: ooo-dev@incubator.apache.org Subject: Re: [RELEASE]: preparation for our first release References: <4F4A1A27.8080308@akerbeltz.org> In-Reply-To: <4F4A1A27.8080308@akerbeltz.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On 2/26/12 12:40 PM, Michael Bauer wrote: >> here we might run into a problem because of not having the translation >> process in place 100%. We have to figure out which translation data is >> the latest one, it's still not 100% clear if we really have it :-( > > Well, for starters, why don't we get the Pootle server up and running, > enable all the languages that were working on localization at the last > known date but keep all data "blank". There will be a fair number of > locales who have local backups of their latest dataset before the old > Pootle server went dead (I know I have) so it would be a simple case of > uploading the po files again. That would solve a number of headaches and > give people the chance to bring them up to date. that is a very important info to know and shows a potential approach. We should start a new thread discussing this further. Juergen > > And *then* worry about the rest. At the moment, everything is dead on > the localization side and if a release is being eyed, then the longer > that's dead, the worse a headache it becomes for the translators. > > Michael