Hi Sergio, I used this line from the Apache release signing doc ( https://www.apache.org/dev/release-signing.html#md5): $ gpg --print-md MD5 [fileName] > [fileName].md5
What is normally used to checksum/verify the md5 and sha hash? As it is now, they can be manually verified by comparing the checksum in the file with one that was derived from the zip. I hope that's still ok for the release to go through? Cheers, Aljoscha On Tue, 25 Oct 2016 at 11:53 Sergio Fernández <[email protected]> wrote: > On Tue, Oct 25, 2016 at 11:36 AM, Jean-Baptiste Onofré <[email protected]> > wrote: > > > By the way, your vote is not binding from a podling perspective (you are > > not PPMC). Your vote is binding from IPMC perspective (so when you will > > vote on the incubator mailing list). > > > > Well, PPMC are never binding votes, only IPMC are actually binding. That > I'm not part of the PPMC is not much relevant. Therefore I think my vote is > still a valid binding one; but I can vote again on general@incubator, no > problem. > > Sorry for jumping-in too early. Besides a IPMC, I'm also a developer > interested in Beam ;-) > > Cheers, > > > > > > On Oct 25, 2016, 11:33, at 11:33, "Sergio Fernández" <[email protected]> > > wrote: > > >+1 (binding) > > > > > >So far I've successfully checked: > > >* signatures and digests > > >* source releases file layouts > > >* matched git tags and commit ids > > >* incubator suffix and disclaimer > > >* NOTICE and LICENSE files > > >* license headers > > >* clean build (Java 1.8.0_91, Scala, 2.11.7, SBT 0.13.9, Debian amd64) > > > > > > > > >Couple of minor issues I've seen it'd be great to have fixed in > > >upcoming > > >releases: > > >* MongoDbIOTest fails (addr already in use) when a Mongo service is > > >locally > > >running. I'd say the port should be random in the test suite. > > >* How did you generated the checksums? Because both SHA1/MD5 can't be > > >automatically checked because "no properly formatted SHA1/MD5 checksum > > >lines found". > > > > > >Great to see the project moving forward at this speed :-) > > > > > >Cheers, > > > > > > > > > > > >On Mon, Oct 24, 2016 at 11:30 PM, Aljoscha Krettek > > ><[email protected]> > > >wrote: > > > > > >> Hi Team! > > >> > > >> Please review and vote at your leisure on release candidate #1 for > > >version > > >> 0.3.0-incubating, as follows: > > >> [ ] +1, Approve the release > > >> [ ] -1, Do not approve the release (please provide specific comments) > > >> > > >> The complete staging area is available for your review, which > > >includes: > > >> * JIRA release notes [1], > > >> * the official Apache source release to be deployed to > > >dist.apache.org > > >> [2], > > >> * all artifacts to be deployed to the Maven Central Repository [3], > > >> * source code tag "v0.3.0-incubating-RC1" [4], > > >> * website pull request listing the release and publishing the API > > >reference > > >> manual [5]. > > >> > > >> Please keep in mind that this release is not focused on providing new > > >> functionality. We want to refine the release process and make stable > > >source > > >> and binary artefacts available to our users. > > >> > > >> The vote will be open for at least 72 hours. It is adopted by > > >majority > > >> approval, with at least 3 PPMC affirmative votes. > > >> > > >> Cheers, > > >> Aljoscha > > >> > > >> [1] > > >> https://issues.apache.org/jira/secure/ReleaseNote.jspa? > > >> projectId=12319527&version=12338051 > > >> [2] https://dist.apache.org/repos/dist/dev/incubator/beam/0.3.0- > > >> incubating/ > > >> [3] > > >> https://repository.apache.org/content/repositories/staging/ > > >> org/apache/beam/ > > >> [4] > > >> https://git-wip-us.apache.org/repos/asf?p=incubator-beam.git;a=tag;h= > > >> 5d86ff7f04862444c266142b0d5acecb5a6b7144 > > >> [5] https://github.com/apache/incubator-beam-site/pull/52 > > >> > > > > > > > > > > > >-- > > >Sergio Fernández > > >Partner Technology Manager > > >Redlink GmbH > > >m: +43 6602747925 <+43%20660%202747925> > > >e: [email protected] > > >w: http://redlink.co > > > > > > -- > Sergio Fernández > Partner Technology Manager > Redlink GmbH > m: +43 6602747925 <+43%20660%202747925> > e: [email protected] > w: http://redlink.co >
