On Jul 12, 2013, at 9:11 AM, Ariel Constenla-Haile wrote: > On Fri, Jul 12, 2013 at 12:48 PM, Rob Weir <robw...@apache.org> wrote: >> Does anyone have a script to verify signatures and hashes for a release? >> >> In previous releases I'd download everything and do some ad-hoc >> commands, but not as automated as it could be. Since we have a >> regular directory structure it should be possible to have a script >> that would verify everything and produce a report. > > unless you are trying to verify the download, there is no need to > download anything, just ssh to people.apache.org and check the > integrity in place once moved to the /www/www.apache.org/dist/ > folder. > Something like: > > arielch@~$ for i in > /home/jsc/public_html/developer-snapshots/RC/4.0.0/binaries/*/*.asc ; > do echo "Checking $i" && gpg2 --verify $i;done
To properly vote on a release requires some verification steps. Rob's idea is one I have been thinking about as well. To the point of a 72 hour VOTE. I think that ONE WEEK would be good for the project if only because it would allow people to adjust their schedules. Personally I prefer the weekend, but a VOTE on Apache OpenOffice took me about 4-8 hours of work for 3.4 and 3.4.1 - and my time is committed this weekend. So, if I have time I'll vote. Otherwise, thanks and I trust the PMC to do what is best for the project. Regards, Dave > > > Regards > > --------------------------------------------------------------------- > 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
