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 3DC9C7032 for ; Thu, 17 Nov 2011 14:15:33 +0000 (UTC) Received: (qmail 94529 invoked by uid 500); 17 Nov 2011 14:15:32 -0000 Delivered-To: apmail-incubator-ooo-dev-archive@incubator.apache.org Received: (qmail 94458 invoked by uid 500); 17 Nov 2011 14:15: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 94374 invoked by uid 99); 17 Nov 2011 14:15:32 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Nov 2011 14:15:32 +0000 X-ASF-Spam-Status: No, hits=-0.6 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of stx123@gmail.com designates 209.85.161.47 as permitted sender) Received: from [209.85.161.47] (HELO mail-fx0-f47.google.com) (209.85.161.47) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Nov 2011 14:15:25 +0000 Received: by faat2 with SMTP id t2so3033035faa.6 for ; Thu, 17 Nov 2011 06:15:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=DHmAP+bnR8UavaCUBdqcMI6B5O7/PV6idmm9G+N2e1Y=; b=sAy9IbZdSs6Fvb27M68+sdvnt9Ghsis2gD2Kucuoe8I1lguh+4bXRhX0IXfdadD4Xb pQxei7LKuJhGILdlAIuOpR29dWnzPghxYFMwmhLikWpdcvxS7itqkQ14vvqVu8ajUPt8 zU/QcEn8YoIH5OD+NG0V8BD90LSrpZg62Klz8= Received: by 10.204.154.77 with SMTP id n13mr33846257bkw.83.1321539304943; Thu, 17 Nov 2011 06:15:04 -0800 (PST) Received: from [192.168.1.28] ([217.110.125.83]) by mx.google.com with ESMTPS id e20sm2225738fab.2.2011.11.17.06.15.02 (version=SSLv3 cipher=OTHER); Thu, 17 Nov 2011 06:15:03 -0800 (PST) Message-ID: <4EC516E3.5030204@gmail.com> Date: Thu, 17 Nov 2011 15:14:59 +0100 From: Stefan Taxhet User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:5.0) Gecko/20110624 Thunderbird/5.0 MIME-Version: 1.0 To: ooo-dev@incubator.apache.org Subject: Re: Non-Apache maintenance release for OOo 3.3? References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi, Am 17.11.2011 02:23, schrieb Rob Weir: > This topic sounds important, so I'm moving it to its own thread. OK, let's talk about a maintenance release first; but at some point we could broaden the scope to releases of Apache OpenOffice too. > On Wed, Nov 16, 2011 at 11:56 AM, Martin Hollmichel > wrote: >> >> removal of the Oracle branding is the easy part. As said before, having a >> joint messaging with ASF about this release and the future releases is some >> work to do. Adopting references from old OpenOffice.org instances (forums, >> mailing lists, issue tracking) to the new ones in the ReadMe File is another >> issue we are still working on. >> > > It is hard to think about a joint message when we know almost nothing > about what you are doing. What we're doing here at Apache is clear -- > you see our mailing lists, wiki, SVN repository, etc. It is all very > open and transparent. > > Do you have a mailing list or something that we can subscribe to? > Could you say a little about what your short term and longer term > goals are? Martin and others mentioned that there is a need to show a sign of life to OpenOffice.org users. For us short term goals are to (re)gain confidence in OpenOffice.org and support for the existing user base. We think this requires a release rather soon; and we don't see a conflict but a complement with work going on in the project here. Long term we want to further sustainable development work. This will result in a reliable product that is improved and delivered at regular intervals. We see such a product as the basis for ongoing business. We are comfortable about continuing the talk here on this list. I would appreciate if we come to a picture that satisfies users, the project and the participants. Greetings Stefan > -Rob > > >> The coding work we've done in the 3.3.1 is about some security and bugfixing >> issues, >> >> Martin >>