Am 06/12/2014 09:01 AM, schrieb Jürgen Schmidt:
On 12/06/14 08:19, Jürgen Schmidt wrote:
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,
https://issues.apache.org/ooo/show_bug.cgi?id=124896
Should be decided by code developers.
124908 remove custom allocator support in stlport-replacement headers,
https://issues.apache.org/ooo/show_bug.cgi?id=124908
Should be decided by code developers.
124422 Build no more possible with Xcode 5.1
https://issues.apache.org/ooo/show_bug.cgi?id=124422
OK, looks reasonable.
124442 Mac and Java Oracle 1.7,
https://issues.apache.org/ooo/show_bug.cgi?id=124442
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.
I had to make a further changes on trunk for building on Mavericks and
clean this up but without an issue :-( I will reuse this issue for
integrate the change.
Juergen
But the message is that I plan to integrate some necessary changes to
make the build possible ;-)
that's always one of the best reasons. When it is not buildable, the
complete software is simply not ready to release. ;-)
Marcus
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
