[DISCUSS] Process: Elect Next Chair of AOO Project Management Committee

[BCC to PMC] [From the Chair] It is time for the selection of the next chair for the Apache OpenOffice Project Management Committee. INCUMBENT CHAIR I officially began my term on the third Wednesday of September, 2015. My commitment was to serve for one full year and then be replaced. I will

Re: Officially releasing a patch for CVE-2016-1513

On 7/31/2016 5:17 PM, Dennis E. Hamilton wrote: -Original Message- From: Kay sch...@apache.org [mailto:ksch...@apache.org] Sent: Sunday, July 31, 2016 14:42 To: dev@openoffice.apache.org Subject: Re: Officially releasing a patch for CVE-2016-1513 OK, I think I'm done with the

Re: Officially releasing a patch for CVE-2016-1513

On 07/31/2016 08:25 AM, Andrea Pescetti wrote: On 30/07/2016 Kay Schenk wrote: duplicate fixed libraries for Linux-32, and Linux-64 based on submissions from Carl, Damjan, and Ariel. I'd be happy to move these somewhere in the next day or so, but I don't know what versions we want to use.

Re: Officially releasing a patch for CVE-2016-1513

On 07/31/2016 05:55 AM, Carl Marcum wrote: > On 07/31/2016 08:25 AM, Andrea Pescetti wrote: >> On 30/07/2016 Kay Schenk wrote: >>> duplicate fixed >>> libraries for Linux-32, and Linux-64 based on submissions from Carl, >>> Damjan, and Ariel. I'd be happy to move these somewhere in the next >>>

Re: Officially releasing a patch for CVE-2016-1513

On 30/07/2016 Kay Schenk wrote: duplicate fixed libraries for Linux-32, and Linux-64 based on submissions from Carl, Damjan, and Ariel. I'd be happy to move these somewhere in the next day or so, but I don't know what versions we want to use. Ariel's were built on a CentOS 5 system, so

Re: Officially releasing a patch for CVE-2016-1513

Am 07/31/2016 08:52 PM, schrieb Kay Schenk: Well...I didn't see this message before I got started and I just finished with Linux32 and used Ariel's patch for this. Of course it can be changed if desired. File size wise, Ariel's patch seemed more in keeping with what I have. You can see what I

RE: Officially releasing a patch for CVE-2016-1513

> -Original Message- > From: Kay Schenk [mailto:kay.sch...@gmail.com] > Sent: Sunday, July 31, 2016 11:53 > To: dev@openoffice.apache.org > Subject: Re: Officially releasing a patch for CVE-2016-1513 [ ... ] > > I won't be doing anything with the Windows area at all, leaving that to >

RE: Officially releasing a patch for CVE-2016-1513

I would prefer that we use Ariel's for the Mac and keep the other Linux ones since those have been accounted for as having been put through the confirmation process and smoke testing. I would like to recognize as many of the contributors as possible. Kay, if you are going to do the uploads of

Re: Officially releasing a patch for CVE-2016-1513

Well...I didn't see this message before I got started and I just finished with Linux32 and used Ariel's patch for this. Of course it can be changed if desired. File size wise, Ariel's patch seemed more in keeping with what I have. You can see what I put on the commit for this. I don't want to get

Re: Officially releasing a patch for CVE-2016-1513

OK, I think I'm done with the LInux64 bit area as well. And see below On 07/31/2016 01:10 PM, Marcus wrote: > Am 07/31/2016 08:52 PM, schrieb Kay Schenk: >> Well...I didn't see this message before I got started and I just >> finished with Linux32 and used Ariel's patch for this. Of course

Re: Any chance to merge the gbuild branch rather soonish?

On 07/30/2016 09:51 PM, Damjan Jovanovic wrote: > The problem is definitely in r1409590, in the LinkTarget.mk patch. > > On Fri, Jul 29, 2016 at 2:12 AM, Damjan Jovanovic wrote: > >> I've narrowed this Windows build performance regression down to the >> original

RE: Officially releasing a patch for CVE-2016-1513

> -Original Message- > From: Kay sch...@apache.org [mailto:ksch...@apache.org] > Sent: Sunday, July 31, 2016 14:42 > To: dev@openoffice.apache.org > Subject: Re: Officially releasing a patch for CVE-2016-1513 > > OK, I think I'm done with the LInux64 bit area as well. > > And see below