Re: [vote] OpenOffice Release Candidate 4.1.6 RC1
Am 02.11.18 um 11:35 schrieb Pedro Lino: > Hi Matthias, all > > >> On November 2, 2018 at 12:33 AM Matthias Seidel > mailto:matthias.sei...@hamburg.de > wrote: >> >> I have just corrected the script to have identical output for SHA256 and >> SHA512. >> > Thank you! It works correctly with any program! > > >> > > AFAIK the data is created by a script. I haven't checked, so it's >>> possible that the way of creation is different for both. Or that >>> they >>> are done by 2 different persons. >>> >>> > >> > > It would be indeed better to have all check sums in the same >> style. >>> > >> > > Is it possible to do this before we have the release? >>> > I remember that we had the same problem with included paths for >>> 4.1.5 >> (Not for Windows files, as I generate them separate for every >> directory). Jim corrected that before the release of 4.1.5. >> > > If your new script is used for all the binaries it would be perfect. I will renew all SHA512 hash files for my Windows builds soon. I only did it for the source first... Maybe Jim can update his files and (if possible) change the script to leave out the paths? Regards, Matthias > > > Best regards, > > Pedro > smime.p7s Description: S/MIME Cryptographic Signature
Re: [vote] OpenOffice Release Candidate 4.1.6 RC1
+1. Il giorno Ven 2 Nov 2018, 11:29 Jim Jagielski ha scritto: > +1 for release! Thx for RMing. > > > On Nov 1, 2018, at 2:52 AM, Peter Kovacs wrote: > > > > Let's try again. > > > > > > Welcome to the vote on Release Candidate 1 for the 4.1.6 Release. > > > > The vote will close on Wednesday the 7.11.2018. > > > > The binaries and the source for testing are to be taken from: > > https://dist.apache.org/repos/dist/dev/openoffice/4.1.6-RC1/ > > > > We follow the policy for the Apache policy on Release Approval at > > http://www.apache.org/legal/release-policy.html#release-approval > > > > In order to create a binding vote individuals are REQUIRED to > > > >* download all signed _source code_ packages onto their own hardware, > > > >* verify that they meet all requirements of ASF policy on releases > >as described below, > > > >* validate all cryptographic signatures, > > > >* compile as provided, and test the result on their own platform. > > > > In order to create a normal vote individuals are REQUIRED to > > > >* download all signed _binary_ packages onto their own hardware, > > > >* verify that they meet all requirements of ASF policy on releases > >as described below, > > > >* validate all cryptographic signatures, > > > >* compile as provided, and test the result on their own platform. > > > > > > > > > The Release Candidate 1 for 4.1.6 has passed my tests. > > > > [+1] yes / +1 > > > > [ ] no / -1 > > > > I have tested > > > > Windows Release > > > >[ ] source / binding > > > >[ ] binary > > > > Linux Release 32 bit > > > >[X] source / binding > > > >[X] binary > > > > Linux Release 64 bit > > > >[X] source / binding > > > >[X] binary > > > > MacOSX Release > > > >[X] source / binding > > > >[X] binary > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > >
Re: [vote] OpenOffice Release Candidate 4.1.6 RC1
Hi Matthias, all > On November 2, 2018 at 12:33 AM Matthias Seidel mailto:matthias.sei...@hamburg.de > wrote: > > I have just corrected the script to have identical output for SHA256 and > SHA512. > Thank you! It works correctly with any program! > > > > AFAIK the data is created by a script. I haven't checked, so it's > > possible that the way of creation is different for both. Or that > > they > > are done by 2 different persons. > > > > > > > > It would be indeed better to have all check sums in the same > style. > > > > > > > > Is it possible to do this before we have the release? > > > > > I remember that we had the same problem with included paths for > > 4.1.5 > (Not for Windows files, as I generate them separate for every > directory). Jim corrected that before the release of 4.1.5. > If your new script is used for all the binaries it would be perfect. Best regards, Pedro
Re: [vote] OpenOffice Release Candidate 4.1.6 RC1
+1 for release! Thx for RMing. > On Nov 1, 2018, at 2:52 AM, Peter Kovacs wrote: > > Let's try again. > > > Welcome to the vote on Release Candidate 1 for the 4.1.6 Release. > > The vote will close on Wednesday the 7.11.2018. > > The binaries and the source for testing are to be taken from: > https://dist.apache.org/repos/dist/dev/openoffice/4.1.6-RC1/ > > We follow the policy for the Apache policy on Release Approval at > http://www.apache.org/legal/release-policy.html#release-approval > > In order to create a binding vote individuals are REQUIRED to > >* download all signed _source code_ packages onto their own hardware, > >* verify that they meet all requirements of ASF policy on releases >as described below, > >* validate all cryptographic signatures, > >* compile as provided, and test the result on their own platform. > > In order to create a normal vote individuals are REQUIRED to > >* download all signed _binary_ packages onto their own hardware, > >* verify that they meet all requirements of ASF policy on releases >as described below, > >* validate all cryptographic signatures, > >* compile as provided, and test the result on their own platform. > > > > The Release Candidate 1 for 4.1.6 has passed my tests. > > [+1] yes / +1 > > [ ] no / -1 > > I have tested > > Windows Release > >[ ] source / binding > >[ ] binary > > Linux Release 32 bit > >[X] source / binding > >[X] binary > > Linux Release 64 bit > >[X] source / binding > >[X] binary > > MacOSX Release > >[X] source / binding > >[X] binary > - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
