> -Original Message-
> From: Andrea Pescetti [mailto:pesce...@apache.org]
> Sent: Tuesday, September 20, 2016 15:59
> To: dev@openoffice.apache.org
> Subject: Re: Tools for building and checking a release candidate
>
> Dennis E. Hamilton wrote:
> >> Fro
> -Original Message-
> From: Dennis E. Hamilton [mailto:dennis.hamil...@acm.org]
> Sent: Tuesday, September 20, 2016 15:18
> To: dev@openoffice.apache.org
> Subject: RE: Tools for building and checking a release candidate
>
>
>
> > -Original Message-
Dennis E. Hamilton wrote:
From: Andrea Pescetti
We are signing. ... Just, we do it in a way that Windows
doesn't like.
It is not about Windows not liking the PGP signatures. It never sees them.
Sure. I wrote that Windows doesn't like the way we sign (detached), not
that it doesn't like the
> -Original Message-
> From: Andrea Pescetti [mailto:pesce...@apache.org]
> Sent: Tuesday, September 20, 2016 14:37
> To: dev@openoffice.apache.org
> Subject: Re: Tools for building and checking a release candidate
>
> On 18/09/2016 Marcus wrote:
> > Am 0
On 9/20/2016 2:37 PM, Andrea Pescetti wrote:
On 18/09/2016 Marcus wrote:
Am 09/17/2016 01:00 PM, schrieb Patricia Shanahan:
Are there any tools to help put together an AOO release? If so, where
are they?
We don't have any. But I've provided a script that I've just used for a
test 4.1.3 build.
On 18/09/2016 Marcus wrote:
Am 09/17/2016 01:00 PM, schrieb Patricia Shanahan:
Are there any tools to help put together an AOO release? If so, where
are they?
We don't have any. But I've provided a script that I've just used for a
test 4.1.3 build. It will find packages in a build tree (after
Am 09/17/2016 01:00 PM, schrieb Patricia Shanahan:
Are there any tools to help put together an AOO release? If so, where
are they?
In particular, the binaries for each language for e.g. Windows will
result from a build in a Windows environment. The release candidate
groups the binaries by langua
