On 1/17/2013 2:45 PM, Kay Schenk wrote:
On Thu, Jan 10, 2013 at 2:23 AM, Oliver-Rainer Wittmann <
orwittm...@googlemail.com> wrote:
Hi,
I have finished the renaming from "OpenOffice.org" to "Apache OpenOffice"
- see issue 121388.
Beside corresponding changes in the user interface this change has impact
on the following important and critical stuff:
- folder/directory names
- package names
- Windows registry key names and values
- ...
As the folder/directory path to the user profile is also changed, the user
profile of a former installed AOO (or OOo) version is not taken over.
If possible, please review the changes in your environment/platform.
I am asking especially our community members working on the BSD platform,
Solaris platform and OS/2 platform to have a deeper look.
minor note:
We are still on version number "3.5.0".
I will work on issue 119977 to adapt the version number to "4.0". I think
I will provide the corresponding patch soon, but I will wait with the
integration in order to have enough time for testing the renaming to
"Apache OpenOffice".
Best regards, Oliver.
I have a quick question but the issue seems to answer this.
This should be included in buildbot output for "trunk" currently, correct?
Given Juergen's recent message about tag SNAPSHOT, I'm a bit confused.
The buildbot output for linux-32-nightly is working and thus should have
output, but the one for linux-32-snapshot is broken.
The snapshot is running on a different box (well, different vm), and I
think I have something I still need to fix on the new vm.
Nightly is running ubuntu 12.04 and snapshot is on ubuntu 10.04. Thus
the snapshot should create 'better' install packages ...
A.
On 23.11.2012 13:04, Oliver-Rainer Wittmann wrote:
Hi,
as we had changed our 'project name' from "OpenOffice.org" to "Apache
OpenOffice" it makes sense to reflect this change also in our source and
the
product based on our source.
We had already made some basic and limited renaming - start center, splash
screen, ... -, but it is not complete.
May be you remember Armin's work on it for our AOO 3.4 (incubating)
release on
branch alg/install. As Armin figured out that the change would be too
risky, we
decided to postpone this name adaption to the next major release.
Thus, I decided to pick up this issue with the goal to solve it for our
next
coming major release.
As there are certain different usages of the name and its variants - e.g.,
visible name of the product, name of the installation directory, ... -
which
impacts quite different areas of our project help is very welcome here.
I will start with investigating Armin's work and documenting the
different usages.
Best regards, Oliver.
