Am 25.01.19 um 19:08 schrieb Mechtilde:
100 % translated Help are German and Dutch:
https://translate.apache.org/projects/aoo40help/
And here the link to the Ui
https://translate.apache.org/projects/aoo40/
You can sort them yourself at the top of the columns
thanks, I thought it would be
Hello Marcus
100 % translated Help are German and Dutch:
https://translate.apache.org/projects/aoo40help/
And here the link to the Ui
https://translate.apache.org/projects/aoo40/
You can sort them yourself at the top of the columns
Regards
Am 25.01.19 um 18:56 schrieb Marcus:
> Am 25.01.19
Am 25.01.19 um 18:39 schrieb Mechtilde:
Am 25.01.19 um 17:29 schrieb Marcus:
Am 10.01.19 um 16:50 schrieb Pedro Giffuni:
do you remember the BZ issues? I would like to add them to the list in
the new release notes (it's a first, very rough draft):
Hello,
Am 25.01.19 um 17:29 schrieb Marcus:
> Am 10.01.19 um 16:50 schrieb Pedro Giffuni:
>
> do you remember the BZ issues? I would like to add them to the list in
> the new release notes (it's a first, very rough draft):
>
>
Am 10.01.19 um 16:50 schrieb Pedro Giffuni:
Thank you to everyone getting involved in the new release. It is very
much needed and I was really tired of the continuous revamping of the
4.1 releases. It is now clear that we are also doing proper branching of
the releases.
Some of the issues
Hi Dave,
Am 18.01.19 um 06:54 schrieb Dave Fisher:
> What action is there to take? It is a valid action by a downstream. Do we
> wish they posted changes upstream? Yes! Can we require it? No!
It was just a funny side note for a fork that claims to be the "real"
successor of OpenOffice.org.
What action is there to take? It is a valid action by a downstream. Do we wish
they posted changes upstream? Yes! Can we require it? No!
Regards,
Dave
Sent from my iPhone
> On Jan 17, 2019, at 9:19 PM, Peter Kovacs wrote:
>
> The Question is:
>
> Do we want to take action here or not?
>
>
The Question is:
Do we want to take action here or not?
On 17.01.19 21:19, Matthias Seidel wrote:
> Hi Marcus,
>
> Am 17.01.19 um 20:42 schrieb Marcus:
>> Am 17.01.19 um 13:41 schrieb Matthias Seidel:
>>> Two of my commits were immediately picked by LO. [1] [2]
>>>
>>> Always nice to see, that
Hi Marcus,
Am 17.01.19 um 20:42 schrieb Marcus:
> Am 17.01.19 um 13:41 schrieb Matthias Seidel:
>> Two of my commits were immediately picked by LO. [1] [2]
>>
>> Always nice to see, that down streaming still works for the fork... :-D
>
> sure, better then to draw this on their own.
>
> Again with
Am 17.01.19 um 13:41 schrieb Matthias Seidel:
Two of my commits were immediately picked by LO. [1] [2]
Always nice to see, that down streaming still works for the fork... :-D
sure, better then to draw this on their own.
Again with a note who has tested and reviewed it - which is totally
Two of my commits were immediately picked by LO. [1] [2]
Always nice to see, that down streaming still works for the fork... :-D
Regards,
Matthias
[1]
https://github.com/LibreOffice/core/commit/28dee1129c7a9c4da34b9253aefd6c6b2df1a073
[2]
+1 from me
up to the time of a beta release
Mechtilde
Am 14.01.19 um 16:46 schrieb Jim Jagielski:
> At this stage, I think just back porting (svn merge) to the AOO42X branch is
> fine.
> As we get close to a release, we'll need to either have an RM approve it
> or so something like creating a
At this stage, I think just back porting (svn merge) to the AOO42X branch is
fine.
As we get close to a release, we'll need to either have an RM approve it
or so something like creating a STATUS file, with a list of proposed backports
and requiring at least 3 +1s to backport (ie: RTC)
> On Jan
Hi Jim,
Am 09.01.19 um 21:54 schrieb Jim Jagielski:
>
>> On Jan 9, 2019, at 3:46 PM, Jim Jagielski wrote:
>>
>> Ahh... something w/ the cppuhelper stuff. Obviously, some UDK issue I'm
>> thinking...
How is the process to get commits merged from trunk to AOO42X?
I adjusted some pointers for
Hey guys!
Thank you to everyone getting involved in the new release. It is very
much needed and I was really tired of the continuous revamping of the
4.1 releases. It is now clear that we are also doing proper branching of
the releases.
Some of the issues off the top of my head that you may
Hello
Am 09.01.19 um 21:21 schrieb Marcus:
> Am 09.01.19 um 20:25 schrieb Mechtilde:
>> thanks for the branch.
>>
>> How do we handle the translation I think we should do the translation on
>> AOOO42X so we only tranlate for the next release.
>
> IMHO yes. But updates need to be done in the
> On Jan 9, 2019, at 3:46 PM, Jim Jagielski wrote:
>
> Ahh... something w/ the cppuhelper stuff. Obviously, some UDK issue I'm
> thinking...
>
Yeppers... for sure it's the udk versioning, which is more a Linux thing than a
macOS (or Windows) thing.
Will look into either hacking around it
Ahh... something w/ the cppuhelper stuff. Obviously, some UDK issue I'm
thinking...
76.372903 : lang : ##
76.372943 : lang : Registering extensions:
76.372991 : lang : ##
76.381173
Request for help...
Any ideas would be helpful:
% build --all:instsetoo_native
build -- version: 1775979
=
Building module instsetoo_native
=
Entering
/Users/jim/src/asf/AOO42X/main/instsetoo_native/inc_openoffice/windows/msi_languages
Entering
Am 09.01.19 um 21:20 schrieb Matthias Seidel:
Am 09.01.19 um 21:12 schrieb Marcus:
Am 09.01.19 um 20:44 schrieb Matthias Seidel:
There is more than minor.mk.
I will try to take care of it...
hm, don't we have now a little script for this? To identify all the
places that need tobe changed?
Am 09.01.19 um 20:25 schrieb Mechtilde:
thanks for the branch.
How do we handle the translation I think we should do the translation on
AOOO42X so we only tranlate for the next release.
IMHO yes. But updates need to be done in the 4.2.x branches directly and
should not come from Pootle
Hi Marcus,
Am 09.01.19 um 21:12 schrieb Marcus:
> Am 09.01.19 um 20:44 schrieb Matthias Seidel:
>> There is more than minor.mk.
>>
>> I will try to take care of it...
>
> hm, don't we have now a little script for this? To identify all the
> places that need tobe changed? IMHO it should be
If so, I don't know of it.
Agreed that such a beastie should exist.
> On Jan 9, 2019, at 3:12 PM, Marcus wrote:
>
> Am 09.01.19 um 20:44 schrieb Matthias Seidel:
>> There is more than minor.mk.
>> I will try to take care of it...
>
> hm, don't we have now a little script for this? To identify
Am 09.01.19 um 20:44 schrieb Matthias Seidel:
There is more than minor.mk.
I will try to take care of it...
hm, don't we have now a little script for this? To identify all the
places that need tobe changed? IMHO it should be somewhere in devtools.
Marcus
Am 09.01.19 um 20:41 schrieb
There is more than minor.mk.
I will try to take care of it...
Am 09.01.19 um 20:41 schrieb Jim Jagielski:
> All done
>
>> On Jan 9, 2019, at 2:21 PM, Matthias Seidel
>> wrote:
>>
>> 9800
>
smime.p7s
Description: S/MIME Cryptographic Signature
All done
> On Jan 9, 2019, at 2:21 PM, Matthias Seidel
> wrote:
>
> 9800
Hello,
thanks for the branch.
How do we handle the translation I think we should do the translation on
AOOO42X so we only tranlate for the next release.
Make sense?
Regards
Mechtilde
Am 09.01.19 um 20:10 schrieb Jim Jagielski:
>
>
>> On Jan 9, 2019, at 1:37 PM, Matthias Seidel
>> wrote:
Am 09.01.19 um 20:10 schrieb Jim Jagielski:
>
>> On Jan 9, 2019, at 1:37 PM, Matthias Seidel
>> wrote:
>>
>> Hi Jim,
>>
>> Am 09.01.19 um 18:40 schrieb Jim Jagielski:
>>> Trunk has been branched off to the (eventual) release branch
>>> for the AOO 4.2.x series. The branch is:
>>>
>>>
+1 to this plan.
On 09.01.19 20:10, Jim Jagielski wrote:
>
>> On Jan 9, 2019, at 1:37 PM, Matthias Seidel
>> wrote:
>>
>> Hi Jim,
>>
>> Am 09.01.19 um 18:40 schrieb Jim Jagielski:
>>> Trunk has been branched off to the (eventual) release branch
>>> for the AOO 4.2.x series. The branch is:
>>>
> On Jan 9, 2019, at 1:37 PM, Matthias Seidel
> wrote:
>
> Hi Jim,
>
> Am 09.01.19 um 18:40 schrieb Jim Jagielski:
>> Trunk has been branched off to the (eventual) release branch
>> for the AOO 4.2.x series. The branch is:
>>
>>
Hi Jim,
Am 09.01.19 um 18:40 schrieb Jim Jagielski:
> Trunk has been branched off to the (eventual) release branch
> for the AOO 4.2.x series. The branch is:
>
> https://svn.apache.org/repos/asf/openoffice/branches/AOO42X
Great, but why is it called 42X? Wouldn't 420 be better?
The reason I
, 2019 11:10 PM
To: OOo Apache
Subject: AOO 4.2.x development branch created
Trunk has been branched off to the (eventual) release branch
for the AOO 4.2.x series. The branch is:
https://svn.apache.org/repos/asf/openoffice/branches/AOO42X
Development can, and should, continue on trunk, but ONLY
Trunk has been branched off to the (eventual) release branch
for the AOO 4.2.x series. The branch is:
https://svn.apache.org/repos/asf/openoffice/branches/AOO42X
Development can, and should, continue on trunk, but ONLY
approved backports should be applied to AOO42X.
Cheers!
33 matches
Mail list logo
