Return-Path: X-Original-To: apmail-openoffice-dev-archive@www.apache.org Delivered-To: apmail-openoffice-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 25D2811770 for ; Sat, 7 Jun 2014 12:03:56 +0000 (UTC) Received: (qmail 26660 invoked by uid 500); 7 Jun 2014 12:03:55 -0000 Delivered-To: apmail-openoffice-dev-archive@openoffice.apache.org Received: (qmail 26572 invoked by uid 500); 7 Jun 2014 12:03:55 -0000 Mailing-List: contact dev-help@openoffice.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@openoffice.apache.org Delivered-To: mailing list dev@openoffice.apache.org Received: (qmail 26562 invoked by uid 99); 7 Jun 2014 12:03:55 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 07 Jun 2014 12:03:55 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy includes SPF record at spf.trusted-forwarder.org) Received: from [208.113.200.129] (HELO homiemail-a58.g.dreamhost.com) (208.113.200.129) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 07 Jun 2014 12:03:51 +0000 Received: from homiemail-a58.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a58.g.dreamhost.com (Postfix) with ESMTP id 90B207D805B; Sat, 7 Jun 2014 05:03:24 -0700 (PDT) Received: from [192.168.0.9] (unknown [151.67.31.44]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: andrea@pescetti.it) by homiemail-a58.g.dreamhost.com (Postfix) with ESMTPSA id D4F207D8058; Sat, 7 Jun 2014 05:03:23 -0700 (PDT) Message-ID: <5392FF8A.60503@apache.org> Date: Sat, 07 Jun 2014 14:03:22 +0200 From: Andrea Pescetti User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: dev@openoffice.apache.org Subject: Re: [RELEASE PLANNING] New release planning template in the Wiki References: <539217D5.6020109@wtnet.de> In-Reply-To: <539217D5.6020109@wtnet.de> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On 06/06/2014 Marcus (OOo) wrote: > https://cwiki.apache.org/confluence/display/OOOUSERS/Release+Planning+Template > As promised some time ago I've now created a schedule plan for a new > release. This will surely be helpful. I made some changes, but I'm confused about the three translation phases. For sure this part is not reflecting reality, we don't have three translation phases. The process is as follows: - We set a deadline for new translations to reach 100% - We set a deadline for existing translations to be fixed in Pootle - We set a deadline for updating/integrating dictionaries - We currently don't set deadlines for the Release notes, but we could The three deadlines can well be the same. And any action requiring code change must be requested in Bugzilla (so: if fixes are made in the French translation, volunteers will open an issue to integrate the fixes; same for any other actions). A translation never "starts": it is always open, and volunteers can ask for import from Pootle when necessary. I don't know how to put this process in the current version of the plan. What did you have in mind with the three translation phases? A full import at the end of each phase? We are not doing that and we won't so long as we use the current technology. Regards, Andrea. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org For additional commands, e-mail: dev-help@openoffice.apache.org