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 6F9EC11002 for ; Wed, 18 Jun 2014 12:10:34 +0000 (UTC) Received: (qmail 98764 invoked by uid 500); 18 Jun 2014 12:10:34 -0000 Delivered-To: apmail-openoffice-dev-archive@openoffice.apache.org Received: (qmail 98682 invoked by uid 500); 18 Jun 2014 12:10:34 -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 98670 invoked by uid 99); 18 Jun 2014 12:10:33 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Jun 2014 12:10:33 +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 jogischmidt@gmail.com designates 209.85.212.180 as permitted sender) Received: from [209.85.212.180] (HELO mail-wi0-f180.google.com) (209.85.212.180) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Jun 2014 12:10:27 +0000 Received: by mail-wi0-f180.google.com with SMTP id hi2so1003204wib.1 for ; Wed, 18 Jun 2014 05:10:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=IFCWb/vbBwKBKGLbJWjOPNPuMtNR8xzcH4MTS8dwI2E=; b=Z0CaH1WzUPYDJ4qdAtqmVQTsnJAcOIjq0U+eKnoS0i+bbSal2uY5UFzbQCapj95iT3 eyO5dL2GH/ICVEVThsy36wRcHFovJucO2q4YCTsauMpPCHe9xjUoTvQ/zBZAdKypYK1q jxBOeA+s2o9f041iHnl8YXViWLj0BA5OQmqrKEd3HeX2S6EMD7EDYdDE+EHDOMNZMRTh 7vXemm8zh8oRS+lkbIiID/UCHQXcFUO2Yz0AMiXuHxMK1ejpoGovCrg2mbsFGHoUsaH/ pzrR6aprdq8kK6zVIXtsGCbrHw42M0rKWnKfpYoNx1kFTNOrSNM5OWtFRsf2CI5KNqXZ 0+kQ== X-Received: by 10.180.206.73 with SMTP id lm9mr4753156wic.54.1403093406146; Wed, 18 Jun 2014 05:10:06 -0700 (PDT) Received: from [9.158.40.77] (gbibp9ph1--blueice4n1.emea.ibm.com. [195.212.29.91]) by mx.google.com with ESMTPSA id c43sm4923902eeg.11.2014.06.18.05.10.04 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 18 Jun 2014 05:10:05 -0700 (PDT) Message-ID: <53A1819C.6030104@gmail.com> Date: Wed, 18 Jun 2014 14:10:04 +0200 From: =?ISO-8859-1?Q?J=FCrgen_Schmidt?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: dev Subject: Re: [RELEASE][PLANNING]: possible date for AOO 4.1.1 References: <53A175A1.505@gmail.com> In-Reply-To: <53A175A1.505@gmail.com> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org Issues for potential updates of dictionaries are required as well Juergen On 18/06/14 13:18, J�rgen Schmidt wrote: > Hi, > > I am currently thinking about a possible release date for AOO 4.1.1 and > believe a date in August would be good. The main question is how long > the QA work will take? > > AOO 4.1.1 will be a bugfix release only with some additional translation > update and potentially new languages. > > A further point is if we make a Beta or not or work with RC candidates > only. Again it is a bugfix release only and every official release (and > a Beta is official) needs more effort. And when I try to reflect the > last Beta I don't think it was very successful. We had >300000 downloads > and thought we would receive the necessary and good feedback we need to > release a good version. AOO 4.1 is good but we have some serious issues > that were not detected during normal Qa and not during the Beta phase of > active Beta users. > > Currently we have 26 issues with granted or requested showstopper flag. > Most of them are already fixed. > > I haven't seen any issue so far a translation update. If issues exist > already please request the showstopper flag asap. > > We have no new strings and I know that update work or fixing of > translation is already ongoing. We should plan in time with a deadline > for translation updates. I think a possible date can be mid of July. We > need a fixed date that people can plan accordingly, otherwise we run > always in the same situation and changes are coming in late. But that > don't scale very well and we should keep deadlines in mind. > > What does others think about it? > > Juergen > > PS: this mail is on dev only because dev is our main mailing list. We > have again the situation that people active on QA or l18n don't read dev > which is problematic because they potentially miss important news for > upcoming releases. But sending info on all lists will result is split > discussion that I would like to avoid. I didn't really worked in the > past, even not with a reply-to filed. Well final deadlines will be > communicated on the qa@ and l18n@ list as well. > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org For additional commands, e-mail: dev-help@openoffice.apache.org