Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ooo-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of acolorado@gmail.com designates
 74.125.82.43 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:content-type;
        b=b6hdlhwA3l6p75S75mMUyrbiGCifzwIwQVB4z7A8VMO9Cndn03F788nf7z6Il6FbA0
         w4x+f3/gwdl/xUpsFH1s7O4+BCCrEfOvUJNyDhOtNsuMLHtKVGcKyoz029KfNFRmUkqn
         ADkjfLAGWJ1uhBHLtY5uSRKhlDxQXkUA3onZQ=
MIME-Version: 1.0
Sender: acolorado@gmail.com
In-Reply-To: <1308479011.2937.45.camel@localhost.localdomain>
References: <1308479011.2937.45.camel@localhost.localdomain>
Date: Sun, 19 Jun 2011 05:44:38 -0500
Message-ID: <BANLkTin2Kbe5oszMYWzsJ4+iWd9CaA0iBg@mail.gmail.com>
Subject: Re: Releasing OOo 3.4 on the old infrastructure
From: Alexandro Colorado <jza@openoffice.org>
To: ooo-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=20cf301fb9832b003004a60e4e3c

--20cf301fb9832b003004a60e4e3c
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Sun, Jun 19, 2011 at 5:23 AM, Andrea Pescetti <pescetti@openoffice.org>w=
rote:

> I understand that the necessary code reorganization in the Apache
> project will forbid a public release for months.
>
> On the other hand, OpenOffice.org 3.4 beta has been out for several
> weeks, is regarded by our QA testers as remarkably stable, has a
> dedicated code line and it is not far from release.
>
> Would it be possible to release OOo 3.4 on the old (Oracle-owned)
> infrastructure, and maybe take advantage of this release to educate
> users and volunteers about the coming new infrastructure at Apache?
>
> This shouldn't require an exceptional effort and it would allow to show
> that OpenOffice.org it in good shape and to use the momentum of a new
> release to communicate better the transition to Apache. Otherwise we
> really risk to confuse users and let them feel abandoned, and work on
> the incubator in the next months could be less useful.
>
> It really seems a small effort compared to the major code refactoring
> needed at Apache, and I believe Oracle can state that the bugfixes on
> the OOo 3.4 code line will be granted to Apache too. And the benefits
> for users and communication would be immense.
>
> Now, I take for granted that the community would support this proposal
> (for one, the Italian community spent weeks to get the OOo 3.4 strings
> 100% translated into Italian, and our QA team is ready to start full
> testing any moment). Would developers and release managers support this
> too?
>
> Regards,
>   Andrea.
>
>  +1 I think this should be a go. I even publish the Beta version on the
'es' homepage so people have a quicker access to it.


--=20
*Alexandro Colorado*
*OpenOffice.org* Espa=C3=B1ol
http://es.openoffice.org

--20cf301fb9832b003004a60e4e3c--