Mailing-List: contact ooo-marketing-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ooo-marketing@incubator.apache.org
MIME-Version: 1.0
In-Reply-To: <005001ccb834$30ca5b80$925f1280$@apache.org>
References: <000f01ccb7a7$4574dd90$d05e98b0$@acm.org>
	<CAP-ksohGD8n=0-t5HEmVHhMGS89awa774NivCGxCh--L6bjRxg@mail.gmail.com>
	<005001ccb834$30ca5b80$925f1280$@apache.org>
Date: Sun, 11 Dec 2011 13:49:36 -0500
Message-ID: 
 <CAP-ksogJkCpvdvm24SB0OQXVjX-j2H9PJhwO5uuzTrQ8o+csgw@mail.gmail.com>
Subject: Re: Distinguishing Apache OpenOffice Releases
From: Rob Weir <robweir@apache.org>
To: ooo-marketing@incubator.apache.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Sun, Dec 11, 2011 at 1:39 PM, Dennis E. Hamilton <orcmid@apache.org> wro=
te:
> I don't think it is our business to replace any non-Apache install of any=
thing, whether OpenOffice.org or LibreOffice, Symphony, whatever.
>

Exactly.  That's the user's business.  If we did anything it would be
to offer to launch the 3rd party uninstall program for the user.  So
the actual uninstall logic would be what was defined by that app.

> It might be useful to offer to import user settings from other products w=
here those are understood and it is benign. =C2=A0I'm wary of bringing over=
 plug-ins installed with other products. =C2=A0A separate tool for that mig=
ht be worthwhile but not sure how much effort it would divert.
>
> And there is always the question of file extension settings being associa=
ted with apps. =C2=A0(There could be multiple associations for power users =
if the apps didn't have identical executable file names all stuck in soffic=
e history.)
>
> Finally, ignoring the technicalities of how close to OpenOffice.org 3.4-d=
ev the first podling release comes, that release is not an OpenOffice.org r=
elease. =C2=A0Users are going to be confused either way. I certainly don't =
want to get in a version-number leap-frog race with LO. =C2=A0(My calculus =
says LO 3.6 will be in site around that time.)
>
> =C2=A0- Dennis
>
>
>
> -----Original Message-----
> From: Rob Weir [mailto:robweir@apache.org]
> Sent: Sunday, December 11, 2011 05:25
> To: ooo-marketing@incubator.apache.org
> Subject: Re: Distinguishing Apache OpenOffice Releases
>
> On Sat, Dec 10, 2011 at 8:50 PM, Dennis E. Hamilton
> <dennis.hamilton@acm.org> wrote:
>> =C2=A0I was thinking that, to the extent that AOO is a reboot of OpenOff=
ice.org, it would be useful to break from the OO.o version-numbering progre=
ssion in some way, especially because the incubator releases have a special=
 status.
>>
>
> Changing the naming pattern would be useful for whom? =C2=A0Not the user,=
 I
> think. =C2=A0Remember, the beta 3.4 was already released. =C2=A0Coming ou=
t with
> anything other than the final 3.4 would be confusing for users.
>
>> =C2=A0I would normally have raised this only on ooo-dev, but it is the c=
onnection with automobile models that had me come here instead.
>>
>> =C2=A0I was thinking that the incubator releases could begin their own d=
istinct progression. =C2=A0My thought was to use identifiers like 3i4, or e=
ven A3i4 (no punctuation marks unless there are dot releases). =C2=A0There =
can also be A3i4-beta, a3i4-rc1, and the like.
>
>>
>
> Maybe there is a more detailed string we could put in the about box?
> I have no objections to that. Ditto for encoding this in the ODF docs.
> =C2=A0We can use that to track dev builds, release candidates, etc. =C2=
=A0This
> is very useful for tracking defect reports, etc.
>
> But from a branding perspective, I think we want to continue the
> exiting numbering scheme. =C2=A0We're trying to project continuity.
>
>> I don't know where that goes beyond incubation. =C2=A0Maybe A3x5 or what=
ever. =C2=A0Even A4x for starters, if it is really that dramatically differ=
ent when incubation exit occurs.
>>
>> On the technical side, it should be possible to install all of these sid=
e-by-side with each other and also with any other release built on an OpenO=
ffice.org legacy model. =C2=A0(There should be an option to upgrade over pr=
evious A3i4, say, but it should not be forced. =C2=A0That's a matter of mak=
ing it easy for someone to back out a release or beta that is a regression =
for them.)
>>
>
> One option is to install into a separate directly, but offer to copy
> settings from an exiting install of OOo or LO. =C2=A0Or offer the user to
> uninstall and replace an existing OOo or LO install. =C2=A0Let the user
> choose.
>
> -Rob
>
>> =C2=A0- Dennis
>>
>>
>>
>>
>>
>>
>