Re: AOO 4.2.x development branch created
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 already more. Then I think we should give people a chance to translate the last few percent for specific languages. Then we have more languages with 100% - UI and/or help. That means include a (longer) translation time frame in the relase plan. Marcus Am 25.01.19 um 18:56 schrieb Marcus: 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): https://cwiki.apache.org/confluence/display/OOOUSERS/Release+Notes+Apache+4.2.0 I add the languages with has 100 % translated UI in Pootle. thanks, are there any new languages with 100% complete Help content? Then we should write this, too, as it is interesting for the users. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: AOO 4.2.x development branch created
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 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): >>> >>> https://cwiki.apache.org/confluence/display/OOOUSERS/Release+Notes+Apache+4.2.0 >>> >> >> I add the languages with has 100 % translated UI in Pootle. > > thanks, are there any new languages with 100% complete Help content? > > Then we should write this, too, as it is interesting for the users. > > Marcus > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > -- Mechtilde Stehmann ## Apache OpenOffice ## Freie Office Suite für Linux, MacOSX, Windows ## Debian Developer ## PGP encryption welcome ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F signature.asc Description: OpenPGP digital signature
Re: AOO 4.2.x development branch created
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): https://cwiki.apache.org/confluence/display/OOOUSERS/Release+Notes+Apache+4.2.0 I add the languages with has 100 % translated UI in Pootle. thanks, are there any new languages with 100% complete Help content? Then we should write this, too, as it is interesting for the users. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: AOO 4.2.x development branch created
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): > > https://cwiki.apache.org/confluence/display/OOOUSERS/Release+Notes+Apache+4.2.0 I add the languages with has 100 % translated UI in Pootle. > > > Thanks > > Marcus > Thanks -- Mechtilde Stehmann ## Apache OpenOffice ## Freie Office Suite für Linux, MacOSX, Windows ## Debian Developer ## PGP encryption welcome ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F signature.asc Description: OpenPGP digital signature
Re: AOO 4.2.x development branch created
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 off the top of my head that you may want to mention on the Release Notes: - All the fonts have been updated. We also added two fonts Caladea and Carlito which are geometrically compatible to Microsoft Cambria and Calibre. - Python was updated to 2.7.15. Hunspell was updated to 1.3.3. - Cleanups for many, many typos everywhere. - Fixed many issues detected by Coverity scan. There are many more changes that I surely forgot about. 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): https://cwiki.apache.org/confluence/display/OOOUSERS/Release+Notes+Apache+4.2.0 Thanks Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: AOO 4.2.x development branch created
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. They forked in 2011(?) but list copyright back to 2000. Maybe here is some action to be taken? Regards, Matthias > > 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? >> >> >>> 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 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 fine - but no hint where it comes from and who is the author. They still don't want to tell where they get the code from. >>> Not exactly, Pilot_Pirx is me... ;-) >>> >>> But now it looks like I would have committed it directly to LO, while >>> they just monitor aoo/trunk and take what they can use. [1] >>> >>> Regards, >>> >>>Matthias >>> >>> [1] >>> https://github.com/LibreOffice/core/commit/1170f10906a9bca78782df6ab1b6a4e20cf0435a >>> Is this redicioulous or just sad? I don't know. :-( Marcus > [1] > https://github.com/LibreOffice/core/commit/28dee1129c7a9c4da34b9253aefd6c6b2df1a073 > > [2] > https://github.com/LibreOffice/core/commit/9796738e1149a99f8b3ff687b0f72264ba3a56ff > > >> 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 STATUS file, with a list of proposed >> backports >> and requiring at least 3 +1s to backport (ie: RTC) >> >>> On Jan 14, 2019, at 10:40 AM, Matthias Seidel >>> wrote: >>> >>> 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 Windows and Linux: >>> >>> https://svn.apache.org/viewvc?view=revision=1851110 >>> https://svn.apache.org/viewvc?view=revision=185 >>> https://svn.apache.org/viewvc?view=revision=1851214 >>> >>> Additionally I updated some pointers for OS/2. I know that Bitwise is >>> already working on a port of 4.2.0, so they would be useful. >>> >>> Since it took me several attempts it would be easier, if I would >>> commit >>> them directly. .. >>> >>> Regards >>> >>> Matthias >>> 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 or something else. I thought I had fixed it. Obviously not :( - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org >> - >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >> For additional commands, e-mail: dev-h...@openoffice.apache.org >> > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > smime.p7s Description: S/MIME Cryptographic Signature
Re: AOO 4.2.x development branch created
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? > > >> 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 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 >>> fine - but no hint where it comes from and who is the author. They >>> still don't want to tell where they get the code from. >> Not exactly, Pilot_Pirx is me... ;-) >> >> But now it looks like I would have committed it directly to LO, while >> they just monitor aoo/trunk and take what they can use. [1] >> >> Regards, >> >>Matthias >> >> [1] >> https://github.com/LibreOffice/core/commit/1170f10906a9bca78782df6ab1b6a4e20cf0435a >> >>> Is this redicioulous or just sad? I don't know. :-( >>> >>> Marcus >>> >>> >>> [1] https://github.com/LibreOffice/core/commit/28dee1129c7a9c4da34b9253aefd6c6b2df1a073 [2] https://github.com/LibreOffice/core/commit/9796738e1149a99f8b3ff687b0f72264ba3a56ff > 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 STATUS file, with a list of proposed > backports > and requiring at least 3 +1s to backport (ie: RTC) > >> On Jan 14, 2019, at 10:40 AM, Matthias Seidel >> wrote: >> >> 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 Windows and Linux: >> >> https://svn.apache.org/viewvc?view=revision=1851110 >> https://svn.apache.org/viewvc?view=revision=185 >> https://svn.apache.org/viewvc?view=revision=1851214 >> >> Additionally I updated some pointers for OS/2. I know that Bitwise is >> already working on a port of 4.2.0, so they would be useful. >> >> Since it took me several attempts it would be easier, if I would >> commit >> them directly. .. >> >> Regards >> >> Matthias >> >>> 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 or something else. I >>> thought I had fixed it. Obviously not :( >>> >>> - >>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >>> For additional commands, e-mail: dev-h...@openoffice.apache.org >>> > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: AOO 4.2.x development branch created
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 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 >> fine - but no hint where it comes from and who is the author. They >> still don't want to tell where they get the code from. > Not exactly, Pilot_Pirx is me... ;-) > > But now it looks like I would have committed it directly to LO, while > they just monitor aoo/trunk and take what they can use. [1] > > Regards, > > Matthias > > [1] > https://github.com/LibreOffice/core/commit/1170f10906a9bca78782df6ab1b6a4e20cf0435a > >> Is this redicioulous or just sad? I don't know. :-( >> >> Marcus >> >> >> >>> [1] >>> https://github.com/LibreOffice/core/commit/28dee1129c7a9c4da34b9253aefd6c6b2df1a073 >>> >>> [2] >>> https://github.com/LibreOffice/core/commit/9796738e1149a99f8b3ff687b0f72264ba3a56ff >>> >>> >>> 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 STATUS file, with a list of proposed backports and requiring at least 3 +1s to backport (ie: RTC) > On Jan 14, 2019, at 10:40 AM, Matthias Seidel > wrote: > > 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 Windows and Linux: > > https://svn.apache.org/viewvc?view=revision=1851110 > https://svn.apache.org/viewvc?view=revision=185 > https://svn.apache.org/viewvc?view=revision=1851214 > > Additionally I updated some pointers for OS/2. I know that Bitwise is > already working on a port of 4.2.0, so they would be useful. > > Since it took me several attempts it would be easier, if I would > commit > them directly. .. > > Regards > > Matthias > >> 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 or something else. I >> thought I had fixed it. Obviously not :( >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >> For additional commands, e-mail: dev-h...@openoffice.apache.org >> - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: AOO 4.2.x development branch created
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 a note who has tested and reviewed it - which is totally > fine - but no hint where it comes from and who is the author. They > still don't want to tell where they get the code from. Not exactly, Pilot_Pirx is me... ;-) But now it looks like I would have committed it directly to LO, while they just monitor aoo/trunk and take what they can use. [1] Regards, Matthias [1] https://github.com/LibreOffice/core/commit/1170f10906a9bca78782df6ab1b6a4e20cf0435a > > Is this redicioulous or just sad? I don't know. :-( > > Marcus > > > >> [1] >> https://github.com/LibreOffice/core/commit/28dee1129c7a9c4da34b9253aefd6c6b2df1a073 >> >> [2] >> https://github.com/LibreOffice/core/commit/9796738e1149a99f8b3ff687b0f72264ba3a56ff >> >> >> 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 STATUS file, with a list of proposed >>> backports >>> and requiring at least 3 +1s to backport (ie: RTC) >>> On Jan 14, 2019, at 10:40 AM, Matthias Seidel wrote: 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 Windows and Linux: https://svn.apache.org/viewvc?view=revision=1851110 https://svn.apache.org/viewvc?view=revision=185 https://svn.apache.org/viewvc?view=revision=1851214 Additionally I updated some pointers for OS/2. I know that Bitwise is already working on a port of 4.2.0, so they would be useful. Since it took me several attempts it would be easier, if I would commit them directly. .. Regards Matthias > 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 or something else. I > thought I had fixed it. Obviously not :( > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > smime.p7s Description: S/MIME Cryptographic Signature
Re: AOO 4.2.x development branch created
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 fine - but no hint where it comes from and who is the author. They still don't want to tell where they get the code from. Is this redicioulous or just sad? I don't know. :-( Marcus [1] https://github.com/LibreOffice/core/commit/28dee1129c7a9c4da34b9253aefd6c6b2df1a073 [2] https://github.com/LibreOffice/core/commit/9796738e1149a99f8b3ff687b0f72264ba3a56ff 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 STATUS file, with a list of proposed backports and requiring at least 3 +1s to backport (ie: RTC) On Jan 14, 2019, at 10:40 AM, Matthias Seidel wrote: 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 Windows and Linux: https://svn.apache.org/viewvc?view=revision=1851110 https://svn.apache.org/viewvc?view=revision=185 https://svn.apache.org/viewvc?view=revision=1851214 Additionally I updated some pointers for OS/2. I know that Bitwise is already working on a port of 4.2.0, so they would be useful. Since it took me several attempts it would be easier, if I would commit them directly. .. Regards Matthias 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 or something else. I thought I had fixed it. Obviously not :( - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: AOO 4.2.x development branch created
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] https://github.com/LibreOffice/core/commit/9796738e1149a99f8b3ff687b0f72264ba3a56ff 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 STATUS file, with a list of proposed backports > and requiring at least 3 +1s to backport (ie: RTC) > >> On Jan 14, 2019, at 10:40 AM, Matthias Seidel >> wrote: >> >> 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 Windows and Linux: >> >> https://svn.apache.org/viewvc?view=revision=1851110 >> https://svn.apache.org/viewvc?view=revision=185 >> https://svn.apache.org/viewvc?view=revision=1851214 >> >> Additionally I updated some pointers for OS/2. I know that Bitwise is >> already working on a port of 4.2.0, so they would be useful. >> >> Since it took me several attempts it would be easier, if I would commit >> them directly. .. >> >> Regards >> >>Matthias >> >>> 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 or something else. I thought I had >>> fixed it. Obviously not :( >>> >>> >>> - >>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >>> For additional commands, e-mail: dev-h...@openoffice.apache.org >>> >>> > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > > smime.p7s Description: S/MIME Cryptographic Signature
Re: AOO 4.2.x development branch created
+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 STATUS file, with a list of proposed backports > and requiring at least 3 +1s to backport (ie: RTC) > >> On Jan 14, 2019, at 10:40 AM, Matthias Seidel >> wrote: >> >> 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 Windows and Linux: >> >> https://svn.apache.org/viewvc?view=revision=1851110 >> https://svn.apache.org/viewvc?view=revision=185 >> https://svn.apache.org/viewvc?view=revision=1851214 >> >> Additionally I updated some pointers for OS/2. I know that Bitwise is >> already working on a port of 4.2.0, so they would be useful. >> >> Since it took me several attempts it would be easier, if I would commit >> them directly. .. >> >> Regards >> >>Matthias >> >>> 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 or something else. I thought I had >>> fixed it. Obviously not :( >>> >>> >>> - >>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >>> For additional commands, e-mail: dev-h...@openoffice.apache.org >>> >>> >> > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > -- Mechtilde Stehmann ## Apache OpenOffice ## Freie Office Suite für Linux, MacOSX, Windows ## Debian Developer ## PGP encryption welcome ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F signature.asc Description: OpenPGP digital signature
Re: AOO 4.2.x development branch created
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 14, 2019, at 10:40 AM, Matthias Seidel > wrote: > > 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 Windows and Linux: > > https://svn.apache.org/viewvc?view=revision=1851110 > https://svn.apache.org/viewvc?view=revision=185 > https://svn.apache.org/viewvc?view=revision=1851214 > > Additionally I updated some pointers for OS/2. I know that Bitwise is > already working on a port of 4.2.0, so they would be useful. > > Since it took me several attempts it would be easier, if I would commit > them directly. .. > > Regards > >Matthias > >>> >> 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 or something else. I thought I had >> fixed it. Obviously not :( >> >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >> For additional commands, e-mail: dev-h...@openoffice.apache.org >> >> > - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: AOO 4.2.x development branch created
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 Windows and Linux: https://svn.apache.org/viewvc?view=revision=1851110 https://svn.apache.org/viewvc?view=revision=185 https://svn.apache.org/viewvc?view=revision=1851214 Additionally I updated some pointers for OS/2. I know that Bitwise is already working on a port of 4.2.0, so they would be useful. Since it took me several attempts it would be easier, if I would commit them directly. .. Regards Matthias >> > 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 or something else. I thought I had > fixed it. Obviously not :( > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > > smime.p7s Description: S/MIME Cryptographic Signature
Re: AOO 4.2.x development branch created
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 want to mention on the Release Notes: - All the fonts have been updated. We also added two fonts Caladea and Carlito which are geometrically compatible to Microsoft Cambria and Calibre. - Python was updated to 2.7.15. Hunspell was updated to 1.3.3. - Cleanups for many, many typos everywhere. - Fixed many issues detected by Coverity scan. There are many more changes that I surely forgot about. Pedro.
Re: AOO 4.2.x development branch created
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 4.2.x branches directly and > should not come from Pootle anymore. > > As soon as it's clear that the 4.2.X release branch is done and found > it's end, new translations for the new 4.3.x branch should then come > again from Pootle. > > At least this is my understanding. We can do the translation for 42x in Pootle as long as I do not merge a template from trunk. For creating the SDF-file I must use the template file which the translation based on. https://wiki.openoffice.org/wiki/Translation_from_4.2 I see no problem to do more translation in Pootle. > > Marcus > Regards -- Mechtilde Stehmann ## Apache OpenOffice ## Freie Office Suite für Linux, MacOSX, Windows ## Debian Developer ## PGP encryption welcome ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F signature.asc Description: OpenPGP digital signature
Re: AOO 4.2.x development branch created
> 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 or something else. I thought I had fixed it. Obviously not :( - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: AOO 4.2.x development branch created
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 : info : ... current dir: /Users/jim/src/asf/AOO42X/main/instsetoo_native/unxmaccx.pro/Apache_OpenOffice/dmg/install/en-US_inprogress/Apache_OpenOffice_4.2.0_MacOS_x86-64_install_en-US/OpenOffice.app/Contents/MacOS ... 76.381393 : lang : Current dir: /Users/jim/src/asf/AOO42X/main/instsetoo_native/unxmaccx.pro/Apache_OpenOffice/dmg/install/en-US_inprogress/Apache_OpenOffice_4.2.0_MacOS_x86-64_install_en-US/OpenOffice.app/Contents/MacOS 76.381469 : info : ... /Users/jim/src/asf/AOO42X/main/instsetoo_native/unxmaccx.pro/Apache_OpenOffice/dmg/install/en-US_inprogress/Apache_OpenOffice_4.2.0_MacOS_x86-64_install_en-US/OpenOffice.app/Contents/program/unopkg sync --verbose -env:UNO_JAVA_JFW_ENV_JREHOME=true 2>&1 | ... 76.381565 : lang : Systemcall: /Users/jim/src/asf/AOO42X/main/instsetoo_native/unxmaccx.pro/Apache_OpenOffice/dmg/install/en-US_inprogress/Apache_OpenOffice_4.2.0_MacOS_x86-64_install_en-US/OpenOffice.app/Contents/program/unopkg sync --verbose -env:UNO_JAVA_JFW_ENV_JREHOME=true 2>&1 | 76.395759 : lang : dyld: Library not loaded: @loader_path/libuno_cppuhelpers5abi.dylib 76.395961 : lang : Referenced from: /Users/jim/src/asf/AOO42X/main/instsetoo_native/unxmaccx.pro/Apache_OpenOffice/dmg/install/en-US_inprogress/Apache_OpenOffice_4.2.0_MacOS_x86-64_install_en-US/OpenOffice.app/Contents/program/libunopkgapp.dylib 76.396012 : lang : Reason: image not found 76.396074 : lang : ERROR: Could not execute "/Users/jim/src/asf/AOO42X/main/instsetoo_native/unxmaccx.pro/Apache_OpenOffice/dmg/install/en-US_inprogress/Apache_OpenOffice_4.2.0_MacOS_x86-64_install_en-US/OpenOffice.app/Contents/program/unopkg sync --verbose -env:UNO_JAVA_JFW_ENV_JREHOME=true 2>&1 |"! Exitcode: '6' - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: AOO 4.2.x development branch created
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 /Users/jim/src/asf/AOO42X/main/instsetoo_native/inc_openoffice/unix Entering /Users/jim/src/asf/AOO42X/main/instsetoo_native/util ... checking environment variables ... make_installer.pl, version 1.0 Product list file: ../util/openoffice.lst Taking setup script from solver Unpackpath: /Users/jim/src/asf/AOO42X/main/instsetoo_native/util/../unxmaccx.pro Compiler: unxmaccx Product: Apache_OpenOffice BuildID: 9800 Build: AOO420 No minor set Product version Using default installpath Package format: dmg msi templatepath: /Users/jim/src/asf/AOO42X/main/instsetoo_native/util/../unxmaccx.pro/misc/openoffice/msi_templates msi template path will be ignored for non Windows builds! msi languagepath: /Users/jim/src/asf/AOO42X/main/instsetoo_native/util/../unxmaccx.pro/misc/win_ulffiles msi language path will be ignored for non Windows builds! Calling epm Stripping files Unzip ARCHIVE files Languages: en-US ... checking required files ... .. searching zip ... Found: /usr/bin/zip ... analyzing ../util/openoffice.lst ... ... reading include paths ... ... analyzing script: /Users/jim/src/asf/AOO42X/main/solver/420/unxmaccx.pro/bin/setup_osl.ins ... ... analyzing script: /Users/jim/src/asf/AOO42X/main/solver/420/unxmaccx.pro/bin/setup_osl.ins ... WARNING: mis-named or un-known %-variable in setup script at line 32927: Description (kab) = "\u1e6c\u1e6def til\u0263uyin tiwurmanin mi ara yewjed umucce\u1e0d amaynut n %PRODUCTNAM."; ... analyzing directories ... ... analyzing files ... ... analyzing scpactions ... ... analyzing shortcuts ... ... analyzing unix links ... ... analyzing profile ... ... analyzing profileitems ... ... analyzing modules ... ... languages en-US ... ... analyzing files ... preparing 1 extension blob for language en-US: dict-en.oxt preparing 0 bundled extensions for language en-US: ... analyzing files with flag ARCHIVE ... ... analyzing files with flag SUBST_FILENAME ... ... analyzing files with flag SCPZIP_REPLACE ... ... analyzing files with flag PATCH_SO_NAME ... ... analyzing files with flag HIDDEN ... ... analyzing all directories for this product ... ... analyzing links ... ... analyzing unix links ... ... creating profiles ... ... analyzing modules ... ... creating installation directory ... ... creating installation set in /Users/jim/src/asf/AOO42X/main/instsetoo_native/unxmaccx.pro/Apache_OpenOffice/dmg/install/en-US ... ... removing old installation directories ... ... creating directories ... ... copying files ... ... creating links ... remove_empty_dirs_in_folder /Users/jim/src/asf/AOO42X/main/instsetoo_native/unxmaccx.pro/Apache_OpenOffice/dmg/install/en-US_inprogress/Apache_OpenOffice_4.2.0_MacOS_x86-64_install_en-US/OpenOffice.app/Contents/share/extensions/install remove_empty_dirs_in_folder /Users/jim/src/asf/AOO42X/main/instsetoo_native/unxmaccx.pro/Apache_OpenOffice/dmg/install/en-US_inprogress/Apache_OpenOffice_4.2.0_MacOS_x86-64_install_en-US/OpenOffice.app/Contents/share/extensions ... current dir: /Users/jim/src/asf/AOO42X/main/instsetoo_native/unxmaccx.pro/Apache_OpenOffice/dmg/install/en-US_inprogress/Apache_OpenOffice_4.2.0_MacOS_x86-64_install_en-US/OpenOffice.app/Contents/MacOS ... ... /Users/jim/src/asf/AOO42X/main/instsetoo_native/unxmaccx.pro/Apache_OpenOffice/dmg/install/en-US_inprogress/Apache_OpenOffice_4.2.0_MacOS_x86-64_install_en-US/OpenOffice.app/Contents/program/unopkg sync --verbose -env:UNO_JAVA_JFW_ENV_JREHOME=true 2>&1 | ... ... cleaning the output tree ... ... removing directory /var/folders/_p/nx0kp5h157197n6ssf35ft7hgn/T/ooopackaging/i_519031547065879 ... ... removing directory /Users/jim/src/asf/AOO42X/main/instsetoo_native/unxmaccx.pro/Apache_OpenOffice/dmg/stripped/en-US ... Error: ERROR: /Users/jim/src/asf/AOO42X/main/instsetoo_native/unxmaccx.pro/Apache_OpenOffice/dmg/install/en-US_inprogress/Apache_OpenOffice_4.2.0_MacOS_x86-64_install_en-US/OpenOffice.app/Contents/program/unopkg sync --verbose -env:UNO_JAVA_JFW_ENV_JREHOME=true 2>&1 | failed! ** ERROR: ERROR: /Users/jim/src/asf/AOO42X/main/instsetoo_native/unxmaccx.pro/Apache_OpenOffice/dmg/install/en-US_inprogress/Apache_OpenOffice_4.2.0_MacOS_x86-64_install_en-US/OpenOffice.app/Contents/program/unopkg sync --verbose -env:UNO_JAVA_JFW_ENV_JREHOME=true 2>&1 | failed! in function: register_extensions ** in function: register_extensionsstopping log at Wed Jan 9 15:32:36 2019 dmake: Error code 255, while making
Re: AOO 4.2.x development branch created
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? IMHO it should be somewhere in devtools. Yes, works for micro releases, we used it for the last release: http://svn.apache.org/repos/asf/openoffice/devtools/updateVersion/ But for a jump in version number there is more to do (according to this issue): https://bz.apache.org/ooo/show_bug.cgi?id=119977 OK, then it should be possible to extend it, so that it can be used for minor and major releases also. Marcus Am 09.01.19 um 20:41 schrieb Jim Jagielski: All done On Jan 9, 2019, at 2:21 PM, Matthias Seidel wrote: 9800 - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: AOO 4.2.x development branch created
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 anymore. As soon as it's clear that the 4.2.X release branch is done and found it's end, new translations for the new 4.3.x branch should then come again from Pootle. At least this is my understanding. Marcus 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: https://svn.apache.org/repos/asf/openoffice/branches/AOO42X Great, but why is it called 42X? Wouldn't 420 be better? The reason is that when it's time to release 4.2.0, we work on 42X until we have it ready. once done, we then tag AOO420 from 42X. That is, the 42X branch will always be the eventual branch for a 4.2.x release. All backports from trunk are done to that branch. Make sense? The reason I ask is because I wanted to adjust the links for the update feed... Development can, and should, continue on trunk, but ONLY approved backports should be applied to AOO42X. Now trunk (aka 420) needs a new internal version number. What about 450? Works for me :) - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: AOO 4.2.x development branch created
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 somewhere in devtools. Yes, works for micro releases, we used it for the last release: http://svn.apache.org/repos/asf/openoffice/devtools/updateVersion/ But for a jump in version number there is more to do (according to this issue): https://bz.apache.org/ooo/show_bug.cgi?id=119977 Regards, Matthias > > Marcus > > > >> Am 09.01.19 um 20:41 schrieb Jim Jagielski: >>> All done >>> On Jan 9, 2019, at 2:21 PM, Matthias Seidel wrote: 9800 > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > smime.p7s Description: S/MIME Cryptographic Signature
Re: AOO 4.2.x development branch created
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 all the places > that need tobe changed? IMHO it should be somewhere in devtools. > > Marcus > > > >> Am 09.01.19 um 20:41 schrieb Jim Jagielski: >>> All done >>> On Jan 9, 2019, at 2:21 PM, Matthias Seidel wrote: 9800 > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: AOO 4.2.x development branch created
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 Jim Jagielski: All done On Jan 9, 2019, at 2:21 PM, Matthias Seidel wrote: 9800 - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: AOO 4.2.x development branch created
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
Re: AOO 4.2.x development branch created
All done > On Jan 9, 2019, at 2:21 PM, Matthias Seidel > wrote: > > 9800
Re: AOO 4.2.x development branch created
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: >> >> 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 is that when it's time to release 4.2.0, we work on 42X until we > have it ready. once done, we then tag AOO420 from 42X. That is, the 42X > branch will always be the eventual branch for a 4.2.x release. All backports > from trunk are done to that branch. > > Make sense? > >> >> The reason I ask is because I wanted to adjust the links for the update >> feed... >> >>> >>> Development can, and should, continue on trunk, but ONLY >>> approved backports should be applied to AOO42X. >> >> Now trunk (aka 420) needs a new internal version number. >> What about 450? >> > > Works for me :) > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > -- Mechtilde Stehmann ## Apache OpenOffice ## Freie Office Suite für Linux, MacOSX, Windows ## Debian Developer ## PGP encryption welcome ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F signature.asc Description: OpenPGP digital signature
Re: AOO 4.2.x development branch created
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: >>> >>>https://svn.apache.org/repos/asf/openoffice/branches/AOO42X >> Great, but why is it called 42X? Wouldn't 420 be better? > The reason is that when it's time to release 4.2.0, we work on 42X until we > have it ready. once done, we then tag AOO420 from 42X. That is, the 42X > branch will always be the eventual branch for a 4.2.x release. All backports > from trunk are done to that branch. > > Make sense? Not really (for me). But I am sure there are others that have an opinion... > >> The reason I ask is because I wanted to adjust the links for the update >> feed... >> >>> Development can, and should, continue on trunk, but ONLY >>> approved backports should be applied to AOO42X. >> Now trunk (aka 420) needs a new internal version number. >> What about 450? >> > Works for me :) At the moment we have two different branches with the same version number (AOO420m1(Build:9800)). We should fix that asap. Regards, Matthias > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > smime.p7s Description: S/MIME Cryptographic Signature
Re: AOO 4.2.x development branch created
+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: >>> >>>https://svn.apache.org/repos/asf/openoffice/branches/AOO42X >> Great, but why is it called 42X? Wouldn't 420 be better? > The reason is that when it's time to release 4.2.0, we work on 42X until we > have it ready. once done, we then tag AOO420 from 42X. That is, the 42X > branch will always be the eventual branch for a 4.2.x release. All backports > from trunk are done to that branch. > > Make sense? > >> The reason I ask is because I wanted to adjust the links for the update >> feed... >> >>> Development can, and should, continue on trunk, but ONLY >>> approved backports should be applied to AOO42X. >> Now trunk (aka 420) needs a new internal version number. >> What about 450? >> > Works for me :) > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: AOO 4.2.x development branch created
> 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: >> >>https://svn.apache.org/repos/asf/openoffice/branches/AOO42X > > Great, but why is it called 42X? Wouldn't 420 be better? The reason is that when it's time to release 4.2.0, we work on 42X until we have it ready. once done, we then tag AOO420 from 42X. That is, the 42X branch will always be the eventual branch for a 4.2.x release. All backports from trunk are done to that branch. Make sense? > > The reason I ask is because I wanted to adjust the links for the update > feed... > >> >> Development can, and should, continue on trunk, but ONLY >> approved backports should be applied to AOO42X. > > Now trunk (aka 420) needs a new internal version number. > What about 450? > Works for me :) - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: AOO 4.2.x development branch created
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 ask is because I wanted to adjust the links for the update feed... > > Development can, and should, continue on trunk, but ONLY > approved backports should be applied to AOO42X. Now trunk (aka 420) needs a new internal version number. What about 450? Regards, Matthias > > Cheers! > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > smime.p7s Description: S/MIME Cryptographic Signature
RE: AOO 4.2.x development branch created
Hi All, Greetings! I’m a hobbyist, after looking at the build issue mails since long time, I have finally ready to contribute to AOO. I have been in the Information Technology since 15 to 16 years. I have seen windows since 3.0 and work on Debian/FreeBSD and also have exposure to couple of other Unix/Linux OS’s. I personally feel that I can contribute to the AOO community. I use AOO on my personal home laptop and desktop(s). I would need a guide/doc to start setting up the build environment on any Linux / Windows. Regards Vittal Sher From: Jim Jagielski Sent: Wednesday, January 9, 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 approved backports should be applied to AOO42X. Cheers! - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
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 approved backports should be applied to AOO42X. Cheers! - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
