AOO 4.2.0-Dev2 (was: macOS and AOO42X)
Hi Mechtilde, Jim, @Mechtilde: French help seems to make some problems (spaces in XML tags). We must check that again. @Jim: I would like to do a complete dev build on Windows to see if all languages are OK. Regards, Matthias Am 03.05.20 um 22:02 schrieb Mechtilde: > +1 > > Am 03.05.20 um 19:58 schrieb Matthias Seidel: >> Hi Jim, >> >> Am 29.04.20 um 20:43 schrieb Jim Jagielski: >>> OK, so I have available a handful of Lang builds for Linux 64bit and macOS >>> available at >>> >>>o http://home.apache.org/~jim/AOO-builds/ >>> >>> These are of HEAD of AOO42X and were built as developer releases... these >>> are not the "official" Dev2m2 releases however, although they are in a >>> directory that implies otherwise. >>> >>> Once people give these a quick A-OK, I can go ahead and do the *real* and >>> *official* Dev2/4.2.0-m2 builds >> All needed languages (including the 5 new ones) are now updated in trunk >> and cherry-picked for AOO42X. >> >> How do we proceed? Create a tag for Dev2? >> I have seen no objections so far, assuming that everyone is OK with it... >> >> 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: macOS and AOO42X
> On May 3, 2020, at 1:58 PM, Matthias Seidel > wrote: > > Hi Jim, > > Am 29.04.20 um 20:43 schrieb Jim Jagielski: >> OK, so I have available a handful of Lang builds for Linux 64bit and macOS >> available at >> >> o http://home.apache.org/~jim/AOO-builds/ >> >> These are of HEAD of AOO42X and were built as developer releases... these >> are not the "official" Dev2m2 releases however, although they are in a >> directory that implies otherwise. >> >> Once people give these a quick A-OK, I can go ahead and do the *real* and >> *official* Dev2/4.2.0-m2 builds > > All needed languages (including the 5 new ones) are now updated in trunk > and cherry-picked for AOO42X. > > How do we proceed? Create a tag for Dev2? > I have seen no objections so far, assuming that everyone is OK with it... > Yep, I think a tag makes the most sense... I'll wait a bit for people to chime in. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: macOS and AOO42X
Hi Jim, Am 04.05.20 um 14:53 schrieb Jim Jagielski: > >> On May 3, 2020, at 1:58 PM, Matthias Seidel >> wrote: >> >> Hi Jim, >> >> Am 29.04.20 um 20:43 schrieb Jim Jagielski: >>> OK, so I have available a handful of Lang builds for Linux 64bit and macOS >>> available at >>> >>> o http://home.apache.org/~jim/AOO-builds/ >>> >>> These are of HEAD of AOO42X and were built as developer releases... these >>> are not the "official" Dev2m2 releases however, although they are in a >>> directory that implies otherwise. >>> >>> Once people give these a quick A-OK, I can go ahead and do the *real* and >>> *official* Dev2/4.2.0-m2 builds >> All needed languages (including the 5 new ones) are now updated in trunk >> and cherry-picked for AOO42X. >> >> How do we proceed? Create a tag for Dev2? >> I have seen no objections so far, assuming that everyone is OK with it... >> > Yep, I think a tag makes the most sense... I'll wait a bit for people to > chime in. Great! As I already wrote, the French language file needs to be fixed, we are working on it... BTW: This time we should really have a Blog post about Dev2. Any volunteers? ;-) 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: macOS and AOO42X
I am OK with the plan. Am 04.05.20 um 14:53 schrieb Jim Jagielski: On May 3, 2020, at 1:58 PM, Matthias Seidel wrote: Hi Jim, Am 29.04.20 um 20:43 schrieb Jim Jagielski: OK, so I have available a handful of Lang builds for Linux 64bit and macOS available at o http://home.apache.org/~jim/AOO-builds/ These are of HEAD of AOO42X and were built as developer releases... these are not the "official" Dev2m2 releases however, although they are in a directory that implies otherwise. Once people give these a quick A-OK, I can go ahead and do the *real* and *official* Dev2/4.2.0-m2 builds All needed languages (including the 5 new ones) are now updated in trunk and cherry-picked for AOO42X. How do we proceed? Create a tag for Dev2? I have seen no objections so far, assuming that everyone is OK with it... Yep, I think a tag makes the most sense... I'll wait a bit for people to chime in. - 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: macOS and AOO42X
Hello >> Yep, I think a tag makes the most sense... I'll wait a bit for people to >> chime in. > > Great! > As I already wrote, the French language file needs to be fixed, we are > working on it... French and Oromoo are fine now. I will do the *.sdf files tomorrow aftr the backup next night. > > BTW: > This time we should really have a Blog post about Dev2. Any volunteers? ;-) > > Regards, > > Matthias Kind regards -- Mechtilde Stehmann ## Apache OpenOffice ## Freie Office Suite für Linux, MacOSX, Windows und OS/2 ## Debian Developer ## PGP encryption welcome ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F signature.asc Description: OpenPGP digital signature
Re: macOS and AOO42X
On 5/4/2020 9:33 AM, Matthias Seidel wrote: > Hi Jim, > > Am 04.05.20 um 14:53 schrieb Jim Jagielski: >> >>> On May 3, 2020, at 1:58 PM, Matthias Seidel >>> wrote: >>> >>> Hi Jim, >>> >>> Am 29.04.20 um 20:43 schrieb Jim Jagielski: OK, so I have available a handful of Lang builds for Linux 64bit and macOS available at o http://home.apache.org/~jim/AOO-builds/ These are of HEAD of AOO42X and were built as developer releases... these are not the "official" Dev2m2 releases however, although they are in a directory that implies otherwise. Once people give these a quick A-OK, I can go ahead and do the *real* and *official* Dev2/4.2.0-m2 builds >>> All needed languages (including the 5 new ones) are now updated in trunk >>> and cherry-picked for AOO42X. >>> >>> How do we proceed? Create a tag for Dev2? >>> I have seen no objections so far, assuming that everyone is OK with it... >>> >> Yep, I think a tag makes the most sense... I'll wait a bit for people to >> chime in. > > Great! > As I already wrote, the French language file needs to be fixed, we are > working on it... > > BTW: > This time we should really have a Blog post about Dev2. Any volunteers? ;-) > > Regards, > > Matthias > >> >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >> For additional commands, e-mail: dev-h...@openoffice.apache.org >> > NOTE: This post is made with my personal hat on. Matthias; I am not sure that a blog post for dev release is a wise idea. To me it would go against the Release Policy As stated at: http://www.apache.org/legal/release-policy.html#publication. Either that or the blog post would need to be carefully worded at a very high level with little detail and must not contain any link to the compiled artifacts at all. I can try my hand at a draft post that I will post here later this evening as I have my grandchildren all day due to a death in the family, but I do not have rights to the Roller Software to publish it. Regards Keith signature.asc Description: OpenPGP digital signature
Re: macOS and AOO42X
Hi Keith, Am 04.05.20 um 17:30 schrieb Keith N. McKenna: > On 5/4/2020 9:33 AM, Matthias Seidel wrote: >> Hi Jim, >> >> Am 04.05.20 um 14:53 schrieb Jim Jagielski: On May 3, 2020, at 1:58 PM, Matthias Seidel wrote: Hi Jim, Am 29.04.20 um 20:43 schrieb Jim Jagielski: > OK, so I have available a handful of Lang builds for Linux 64bit and > macOS available at > > o http://home.apache.org/~jim/AOO-builds/ > > These are of HEAD of AOO42X and were built as developer releases... these > are not the "official" Dev2m2 releases however, although they are in a > directory that implies otherwise. > > Once people give these a quick A-OK, I can go ahead and do the *real* and > *official* Dev2/4.2.0-m2 builds All needed languages (including the 5 new ones) are now updated in trunk and cherry-picked for AOO42X. How do we proceed? Create a tag for Dev2? I have seen no objections so far, assuming that everyone is OK with it... >>> Yep, I think a tag makes the most sense... I'll wait a bit for people to >>> chime in. >> Great! >> As I already wrote, the French language file needs to be fixed, we are >> working on it... >> >> BTW: >> This time we should really have a Blog post about Dev2. Any volunteers? ;-) >> >> Regards, >> >> Matthias >> >>> >>> - >>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >>> For additional commands, e-mail: dev-h...@openoffice.apache.org >>> > NOTE: This post is made with my personal hat on. > Matthias; > > I am not sure that a blog post for dev release is a wise idea. To me it > would go against the Release Policy As stated at: > http://www.apache.org/legal/release-policy.html#publication. Either that > or the blog post would need to be carefully worded at a very high level > with little detail and must not contain any link to the compiled > artifacts at all. If I read that URL right a Blog post would really be inappropriate... But then, the whole Dev Build is useless, if nobody is supposed to know of it. In the end that's why we make a "Developer Snapshot" branded version. ;-) > > I can try my hand at a draft post that I will post here later this > evening as I have my grandchildren all day due to a death in the family, > but I do not have rights to the Roller Software to publish it. I think Marcus has rights on Roller. Regards, Matthias > > > Regards > Keith > > > smime.p7s Description: S/MIME Cryptographic Signature
Re: macOS and AOO42X
On 5/4/2020 11:40 AM, Matthias Seidel wrote: > Hi Keith, > Hi Matthias Comments in line > Am 04.05.20 um 17:30 schrieb Keith N. McKenna: >> On 5/4/2020 9:33 AM, Matthias Seidel wrote: >>> Hi Jim, >>> >>> Am 04.05.20 um 14:53 schrieb Jim Jagielski: > On May 3, 2020, at 1:58 PM, Matthias Seidel > wrote: > > Hi Jim, > > Am 29.04.20 um 20:43 schrieb Jim Jagielski: >> OK, so I have available a handful of Lang builds for Linux 64bit and >> macOS available at >> >> o http://home.apache.org/~jim/AOO-builds/ >> >> These are of HEAD of AOO42X and were built as developer releases... >> these are not the "official" Dev2m2 releases however, although they are >> in a directory that implies otherwise. >> >> Once people give these a quick A-OK, I can go ahead and do the *real* >> and *official* Dev2/4.2.0-m2 builds > All needed languages (including the 5 new ones) are now updated in trunk > and cherry-picked for AOO42X. > > How do we proceed? Create a tag for Dev2? > I have seen no objections so far, assuming that everyone is OK with it... > Yep, I think a tag makes the most sense... I'll wait a bit for people to chime in. >>> Great! >>> As I already wrote, the French language file needs to be fixed, we are >>> working on it... >>> >>> BTW: >>> This time we should really have a Blog post about Dev2. Any volunteers? ;-) >>> >>> Regards, >>> >>> Matthias >>> - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org >> NOTE: This post is made with my personal hat on. >> Matthias; >> >> I am not sure that a blog post for dev release is a wise idea. To me it >> would go against the Release Policy As stated at: >> http://www.apache.org/legal/release-policy.html#publication. Either that >> or the blog post would need to be carefully worded at a very high level >> with little detail and must not contain any link to the compiled >> artifacts at all. > > If I read that URL right a Blog post would really be inappropriate... > > But then, the whole Dev Build is useless, if nobody is supposed to know > of it. > In the end that's why we make a "Developer Snapshot" branded version. ;-) > he dev builds are fine as long as they are announced on dev@. See the following quote from the policy.> The only people who are supposed to know about such developer resources are individuals actively participating in development or following the dev list and thus aware of the conditions placed on unreleased materials. Given that statement I would recommend against a blog post. Lets wait and see if any others chime in on this. Though I will start a possible post tonight after I take the kids home. Regards Keith. >> >> I can try my hand at a draft post that I will post here later this >> evening as I have my grandchildren all day due to a death in the family, >> but I do not have rights to the Roller Software to publish it. > > I think Marcus has rights on Roller. > > Regards, > > Matthias > >> >> >> Regards >> Keith >> >> >> > signature.asc Description: OpenPGP digital signature
Re: macOS and AOO42X
Am 04.05.20 um 19:16 schrieb Keith N. McKenna: On 5/4/2020 11:40 AM, Matthias Seidel wrote: Hi Keith, Hi Matthias Comments in line Am 04.05.20 um 17:30 schrieb Keith N. McKenna: On 5/4/2020 9:33 AM, Matthias Seidel wrote: Hi Jim, Am 04.05.20 um 14:53 schrieb Jim Jagielski: On May 3, 2020, at 1:58 PM, Matthias Seidel wrote: Hi Jim, Am 29.04.20 um 20:43 schrieb Jim Jagielski: OK, so I have available a handful of Lang builds for Linux 64bit and macOS available at o http://home.apache.org/~jim/AOO-builds/ These are of HEAD of AOO42X and were built as developer releases... these are not the "official" Dev2m2 releases however, although they are in a directory that implies otherwise. Once people give these a quick A-OK, I can go ahead and do the *real* and *official* Dev2/4.2.0-m2 builds All needed languages (including the 5 new ones) are now updated in trunk and cherry-picked for AOO42X. How do we proceed? Create a tag for Dev2? I have seen no objections so far, assuming that everyone is OK with it... Yep, I think a tag makes the most sense... I'll wait a bit for people to chime in. Great! As I already wrote, the French language file needs to be fixed, we are working on it... BTW: This time we should really have a Blog post about Dev2. Any volunteers? ;-) Regards, Matthias - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org NOTE: This post is made with my personal hat on. Matthias; I am not sure that a blog post for dev release is a wise idea. To me it would go against the Release Policy As stated at: http://www.apache.org/legal/release-policy.html#publication. Either that or the blog post would need to be carefully worded at a very high level with little detail and must not contain any link to the compiled artifacts at all. If I read that URL right a Blog post would really be inappropriate... But then, the whole Dev Build is useless, if nobody is supposed to know of it. In the end that's why we make a "Developer Snapshot" branded version. ;-) he dev builds are fine as long as they are announced on dev@. See the following quote from the policy.> The only people who are supposed to know about such developer resources are individuals actively participating in development or following the dev list and thus aware of the conditions placed on unreleased materials. I also think that - in this case - a posting on @dev is the best we can do. So, Keith you still can try to draft the text. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: macOS and AOO42X
Just installed the linux 64 bit, en-US on my machine. All good so far with just few documents. Onto to Calc later. Regards, Kay On 5/4/20 5:53 AM, Jim Jagielski wrote: On May 3, 2020, at 1:58 PM, Matthias Seidel wrote: Hi Jim, Am 29.04.20 um 20:43 schrieb Jim Jagielski: OK, so I have available a handful of Lang builds for Linux 64bit and macOS available at o http://home.apache.org/~jim/AOO-builds/ These are of HEAD of AOO42X and were built as developer releases... these are not the "official" Dev2m2 releases however, although they are in a directory that implies otherwise. Once people give these a quick A-OK, I can go ahead and do the *real* and *official* Dev2/4.2.0-m2 builds All needed languages (including the 5 new ones) are now updated in trunk and cherry-picked for AOO42X. How do we proceed? Create a tag for Dev2? I have seen no objections so far, assuming that everyone is OK with it... Yep, I think a tag makes the most sense... I'll wait a bit for people to chime in. - 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: macOS and AOO42X
On 5/4/2020 1:27 PM, Marcus wrote: > Am 04.05.20 um 19:16 schrieb Keith N. McKenna: >> On 5/4/2020 11:40 AM, Matthias Seidel wrote: >>> Hi Keith, >>> Hi Matthias Comments in line >>> Am 04.05.20 um 17:30 schrieb Keith N. McKenna: On 5/4/2020 9:33 AM, Matthias Seidel wrote: > Hi Jim, > > Am 04.05.20 um 14:53 schrieb Jim Jagielski: >>> On May 3, 2020, at 1:58 PM, Matthias Seidel >>> wrote: >>> >>> Hi Jim, >>> >>> Am 29.04.20 um 20:43 schrieb Jim Jagielski: OK, so I have available a handful of Lang builds for Linux 64bit and macOS available at o http://home.apache.org/~jim/AOO-builds/ These are of HEAD of AOO42X and were built as developer releases... these are not the "official" Dev2m2 releases however, although they are in a directory that implies otherwise. Once people give these a quick A-OK, I can go ahead and do the *real* and *official* Dev2/4.2.0-m2 builds >>> All needed languages (including the 5 new ones) are now updated >>> in trunk >>> and cherry-picked for AOO42X. >>> >>> How do we proceed? Create a tag for Dev2? >>> I have seen no objections so far, assuming that everyone is OK >>> with it... >>> >> Yep, I think a tag makes the most sense... I'll wait a bit for >> people to chime in. > Great! > As I already wrote, the French language file needs to be fixed, we are > working on it... > > BTW: > This time we should really have a Blog post about Dev2. Any > volunteers? ;-) > > Regards, > > Matthias > >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >> For additional commands, e-mail: dev-h...@openoffice.apache.org >> NOTE: This post is made with my personal hat on. Matthias; I am not sure that a blog post for dev release is a wise idea. To me it would go against the Release Policy As stated at: http://www.apache.org/legal/release-policy.html#publication. Either that or the blog post would need to be carefully worded at a very high level with little detail and must not contain any link to the compiled artifacts at all. >>> >>> If I read that URL right a Blog post would really be inappropriate... >>> >>> But then, the whole Dev Build is useless, if nobody is supposed to know >>> of it. >>> In the end that's why we make a "Developer Snapshot" branded version. >>> ;-) >>> >> he dev builds are fine as long as they are announced on dev@. See the >> following quote from the policy.> The only people who are supposed to >> know about such developer resources are individuals actively >> participating in development or following the dev list and thus aware of >> the conditions placed on unreleased materials. > > I also think that - in this case - a posting on @dev is the best we can > do. So, Keith you still can try to draft the text. > > Marcus Sounds good to me Marcus, I will work on that draft later today. Regards Keith signature.asc Description: OpenPGP digital signature
Re: macOS and AOO42X
> On May 4, 2020, at 1:49 PM, Keith N. McKenna > wrote: > > On 5/4/2020 1:27 PM, Marcus wrote: >> Am 04.05.20 um 19:16 schrieb Keith N. McKenna: >>> On 5/4/2020 11:40 AM, Matthias Seidel wrote: Hi Keith, Hi Matthias Comments in line Am 04.05.20 um 17:30 schrieb Keith N. McKenna: > On 5/4/2020 9:33 AM, Matthias Seidel wrote: >> Hi Jim, >> >> Am 04.05.20 um 14:53 schrieb Jim Jagielski: On May 3, 2020, at 1:58 PM, Matthias Seidel wrote: Hi Jim, Am 29.04.20 um 20:43 schrieb Jim Jagielski: > OK, so I have available a handful of Lang builds for Linux 64bit > and macOS available at > >o http://home.apache.org/~jim/AOO-builds/ > > These are of HEAD of AOO42X and were built as developer > releases... these are not the "official" Dev2m2 releases > however, although they are in a directory that implies otherwise. > > Once people give these a quick A-OK, I can go ahead and do the > *real* and *official* Dev2/4.2.0-m2 builds All needed languages (including the 5 new ones) are now updated in trunk and cherry-picked for AOO42X. How do we proceed? Create a tag for Dev2? I have seen no objections so far, assuming that everyone is OK with it... >>> Yep, I think a tag makes the most sense... I'll wait a bit for >>> people to chime in. >> Great! >> As I already wrote, the French language file needs to be fixed, we are >> working on it... >> >> BTW: >> This time we should really have a Blog post about Dev2. Any >> volunteers? ;-) >> >> Regards, >> >> Matthias >> >>> >>> - >>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >>> For additional commands, e-mail: dev-h...@openoffice.apache.org >>> > NOTE: This post is made with my personal hat on. > Matthias; > > I am not sure that a blog post for dev release is a wise idea. To me it > would go against the Release Policy As stated at: > http://www.apache.org/legal/release-policy.html#publication. Either > that > or the blog post would need to be carefully worded at a very high level > with little detail and must not contain any link to the compiled > artifacts at all. If I read that URL right a Blog post would really be inappropriate... But then, the whole Dev Build is useless, if nobody is supposed to know of it. In the end that's why we make a "Developer Snapshot" branded version. ;-) >>> he dev builds are fine as long as they are announced on dev@. See the >>> following quote from the policy.> The only people who are supposed to >>> know about such developer resources are individuals actively >>> participating in development or following the dev list and thus aware of >>> the conditions placed on unreleased materials. >> >> I also think that - in this case - a posting on @dev is the best we can >> do. So, Keith you still can try to draft the text. >> >> Marcus > Sounds good to me Marcus, I will work on that draft later today. I think we could have a blog post asking that anyone who wants to help test development builds should join us on dev@openoffice.apache.org Regards, Dave > > Regards > Keith > - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
