openoffice-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jürgen Schmidt <>
Subject Re: [RELEASE]: AOO 4.1.1 code base and some additional proposed fixes
Date Thu, 12 Jun 2014 06:19:48 GMT
On 11/06/14 19:51, Marcus (OOo) wrote:
> Am 06/11/2014 11:14 AM, schrieb Jürgen Schmidt:
>> Hi,
>> a possible schedule for AOO 4.1.1 is not yet finally discussed and
>> defined but I would like to propose some further issues that are related
>> to make the code working on MacOS 10.9.3.
>> First I propose that we develop the AOO 4.1.1 on the existing branch
>> AOO410 because it should be a minor bugfix release with some translation
>> updates. But no bigger features.
> Don't we have created a branch for every new release even when it was a
> micro release like 4.1.1? To keep a clean repository for those who want
> to build a specific release from scratch?
> Or will you do some magic with SVN tags to reach this?

no magic, but the difference between a branch and a tag is minimal. I
would create a new branch based on branch AOO410. The release version is
tagged and we tag the 4.1.1 as well.

>> And we still have no Mac build bot but I have updated my Mac where I
>> have built the release in the past. Means I have no 10.7 system in place
>> and have to build on MacOs 10.9.3. We made these changes already on
>> trunk and I propose the following issues for integration in AOO 4.1.1 to
>> make the build possible on MacOS 10.9.3. It will still work on 10.7.
>> Well I have already prepared a build and did a first basic test but it
>> will need some more testing of course.
>> The issues are:
>> 124896 remove obsoleted module-internal custom allocator in SAL,
> Should be decided by code developers.
>> 124908 remove custom allocator support in stlport-replacement headers,
> Should be decided by code developers.
>> 124422 Build no more possible with Xcode 5.1
> OK, looks reasonable.
>> 124442 Mac and Java Oracle 1.7,
> The last issue should be already fixed in AOO 4.1.0. Thats what I
> understood from the issue text and target milestone. ;-)

I will check it, maybe I picked the wrong one.

But the message is that I plan to integrate some necessary changes to
make the build possible ;-)


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message