Re: [VOTE] Release 0.3.0-incubating, release candidate #1
The voting time has elapsed. I'm hereby closing this vote and will tally the results in a separate thread. On Thu, 27 Oct 2016 at 17:38 Neelesh Salian wrote: > +1 (non-binding) > Thank you for putting this together > > > On Thu, Oct 27, 2016 at 12:00 AM, Jean-Baptiste Onofré > wrote: > > > No problem for the vote. > > > > For graduation, we are already thinking about it yes. > > > > Regards > > JB > > > > > > > > On Oct 27, 2016, 08:54, at 08:54, "Sergio Fernández" > > wrote: > > >Hi JB, > > > > > >On Tue, Oct 25, 2016 at 12:00 PM, Jean-Baptiste Onofré > > > > > >wrote: > > > > > >> Thanks Sergio ;) > > >> > > > > > >You are welcome. > > > > > > > > >> Just tried to explain to the others what is a binding vote ;) > > >> > > > > > >It's a common mistake in many podlings that PPMC members thing they > > >have > > >binding votes over developers who are not part of the project. But > > >during > > >incubation only IPMC are binding votes. I hope that's clear. > > > > > >In theory it's simple. So sorry if I've made some noise with that. I'll > > >repeat my vote later at general@incubator if you prefer it in that way. > > > > > >Cheers, > > > > > >P.S.: after 0.3.0-incubating, are you thinking about graduation? I > > >think > > >you should ;-) > > > > > > > > > > > >On Oct 25, 2016, 11:53, at 11:53, "Sergio Fernández" > > > > > >> wrote: > > >> >On Tue, Oct 25, 2016 at 11:36 AM, Jean-Baptiste Onofré > > >> > > > >> >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" > > >> > > > >> >> 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 > > >> >> > > > >> >> >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.or
Re: [VOTE] Release 0.3.0-incubating, release candidate #1
+1 (non-binding) Thank you for putting this together On Thu, Oct 27, 2016 at 12:00 AM, Jean-Baptiste Onofré wrote: > No problem for the vote. > > For graduation, we are already thinking about it yes. > > Regards > JB > > > > On Oct 27, 2016, 08:54, at 08:54, "Sergio Fernández" > wrote: > >Hi JB, > > > >On Tue, Oct 25, 2016 at 12:00 PM, Jean-Baptiste Onofré > > > >wrote: > > > >> Thanks Sergio ;) > >> > > > >You are welcome. > > > > > >> Just tried to explain to the others what is a binding vote ;) > >> > > > >It's a common mistake in many podlings that PPMC members thing they > >have > >binding votes over developers who are not part of the project. But > >during > >incubation only IPMC are binding votes. I hope that's clear. > > > >In theory it's simple. So sorry if I've made some noise with that. I'll > >repeat my vote later at general@incubator if you prefer it in that way. > > > >Cheers, > > > >P.S.: after 0.3.0-incubating, are you thinking about graduation? I > >think > >you should ;-) > > > > > > > >On Oct 25, 2016, 11:53, at 11:53, "Sergio Fernández" > > > >> wrote: > >> >On Tue, Oct 25, 2016 at 11:36 AM, Jean-Baptiste Onofré > >> > > >> >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" > >> > > >> >> 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 > >> >> > > >> >> >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 > >> >> >
Re: [VOTE] Release 0.3.0-incubating, release candidate #1
No problem for the vote. For graduation, we are already thinking about it yes. Regards JB On Oct 27, 2016, 08:54, at 08:54, "Sergio Fernández" wrote: >Hi JB, > >On Tue, Oct 25, 2016 at 12:00 PM, Jean-Baptiste Onofré > >wrote: > >> Thanks Sergio ;) >> > >You are welcome. > > >> Just tried to explain to the others what is a binding vote ;) >> > >It's a common mistake in many podlings that PPMC members thing they >have >binding votes over developers who are not part of the project. But >during >incubation only IPMC are binding votes. I hope that's clear. > >In theory it's simple. So sorry if I've made some noise with that. I'll >repeat my vote later at general@incubator if you prefer it in that way. > >Cheers, > >P.S.: after 0.3.0-incubating, are you thinking about graduation? I >think >you should ;-) > > > >On Oct 25, 2016, 11:53, at 11:53, "Sergio Fernández" > >> wrote: >> >On Tue, Oct 25, 2016 at 11:36 AM, Jean-Baptiste Onofré >> > >> >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" >> > >> >> 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 >> >> > >> >> >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 >> >> >e: sergio.fernan...@redlink.co >> >> >w: http://redlink.co >> >> >> > >> > >> > >> >-- >> >Sergio Fernández >> >Partner Technology Manager >> >Redlink GmbH >> >m: +43 6602747925 >> >e: sergio.fernan...@redlink.co >> >w: http://redlink.co >> > > > >-- >Sergio Fernández >Partner Technology Manager >Redlink GmbH >m: +43 6602747925 >e: sergio.fernan...@redlink.co >w: http://redlink.co
Re: [VOTE] Release 0.3.0-incubating, release candidate #1
Hi JB, On Tue, Oct 25, 2016 at 12:00 PM, Jean-Baptiste Onofré wrote: > Thanks Sergio ;) > You are welcome. > Just tried to explain to the others what is a binding vote ;) > It's a common mistake in many podlings that PPMC members thing they have binding votes over developers who are not part of the project. But during incubation only IPMC are binding votes. I hope that's clear. In theory it's simple. So sorry if I've made some noise with that. I'll repeat my vote later at general@incubator if you prefer it in that way. Cheers, P.S.: after 0.3.0-incubating, are you thinking about graduation? I think you should ;-) On Oct 25, 2016, 11:53, at 11:53, "Sergio Fernández" > wrote: > >On Tue, Oct 25, 2016 at 11:36 AM, Jean-Baptiste Onofré > > > >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" > > > >> 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 > >> > > >> >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 > >> >e: sergio.fernan...@redlink.co > >> >w: http://redlink.co > >> > > > > > > > >-- > >Sergio Fernández > >Partner Technology Manager > >Redlink GmbH > >m: +43 6602747925 > >e: sergio.fernan...@redlink.co > >w: http://redlink.co > -- Sergio Fernández Partner Technology Manager Redlink GmbH m: +43 6602747925 e: sergio.fernan...@redlink.co w: http://redlink.co
Re: [VOTE] Release 0.3.0-incubating, release candidate #1
Hi Aljoscha, On Tue, Oct 25, 2016 at 12:06 PM, Aljoscha Krettek wrote: > > 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? > Well, I think is just how the hash is formatted. Normally it's preferable to have to the simple hash, as the maven-gpg-plugin generates (e.g., https://dist.apache.org/repos/dist/release/marmotta/3.3.0/apache- marmotta-3.3.0-src.zip.md5). So you can easily automatically check (md5sum -c foo.md5). I've just outline a PR [1] to fix the issue [2], so we can discuss it over the code. Hope that helps. Cheers, [1] https://github.com/apache/incubator-beam/pull/1206 [2] https://issues.apache.org/jira/browse/BEAM-841 On Tue, 25 Oct 2016 at 11:53 Sergio Fernández wrote: > > > On Tue, Oct 25, 2016 at 11:36 AM, Jean-Baptiste Onofré > > 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" < > wik...@apache.org> > > > 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 > > > > > > > >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: sergio.fernan...@redlink.co > > > >w: http://redlink.co > > > > > > > > > > > -- > > Sergio Fernández > > Partner Technology Manager > > Redlink GmbH > > m: +43 6602747925 <+43%20660%202747925> > > e: sergio.fernan...@redlink.co
Re: [VOTE] Release 0.3.0-incubating, release candidate #1
+1 (binding) On Wed, Oct 26, 2016 at 10:53 AM Maximilian Michels wrote: > +1 (binding) > > Thanks for managing the release, Aljoscha! > > -Max > > > On Wed, Oct 26, 2016 at 6:46 AM, Jean-Baptiste Onofré > wrote: > > Agree. We already discussed about that on the mailing list. I mentionned > this some weeks ago. > > > > Regards > > JB > > > > > > > > On Oct 26, 2016, 02:26, at 02:26, Dan Halperin > wrote: > >>My reading of the LEGAL threads is that since we are not including > >>(shading > >>or bundling) the ASL-licensed code we are fine to distribute kinesis-io > >>module. This was the original conclusion that LEGAL-198 got to, and > >>that > >>thread has not been resolved differently (even if Spark went ahead and > >>broke the assembly). The beam-sdks-java-io-kinesis module is an > >>optional > >>part (Beam materially works just fine without it). > >> > >>So I think we're fine to keep this vote open. > >> > >>+1 (binding) on the release > >> > >>Thanks Aljoscha! > >> > >> > >>On Tue, Oct 25, 2016 at 12:07 PM, Aljoscha Krettek > >> > >>wrote: > >> > >>> Yep, I was looking at those same threads when I reviewing the > >>artefacts. > >>> The release was already close to being finished so I went through > >>with it > >>> but if we think it's not good to have them in we should quickly > >>cancel in > >>> favour of a new RC without a published Kinesis connector. > >>> > >>> On Tue, 25 Oct 2016 at 20:46 Dan Halperin > >> > >>> wrote: > >>> > >>> > I can't tell whether it is a problem that we are distributing the > >>> > beam-sdks-java-io-kinesis module [0]. > >>> > > >>> > Here is the dev@ discussion thread [1] and the (unanswered) > >>relevant > >>> LEGAL > >>> > thread [2]. > >>> > We linked through to a Spark-related discussion [3], and here is > >>how to > >>> > disable distribution of the KinesisIO module [4]. > >>> > > >>> > [0] > >>> > > >>> > https://repository.apache.org/content/repositories/staging/ > >>> org/apache/beam/beam-sdks-java-io-kinesis/ > >>> > [1] > >>> > > >>> > https://lists.apache.org/thread.html/6784bc005f329d93fd59d0f8759ed4 > >>> 745e72f105e39d869e094d9645@%3Cdev.beam.apache.org%3E > >>> > [2] > >>> > > >>> > https://issues.apache.org/jira/browse/LEGAL-198? > >>> focusedCommentId=15471529&page=com.atlassian.jira. > >>> plugin.system.issuetabpanels:comment-tabpanel#comment-15471529 > >>> > [3] https://issues.apache.org/jira/browse/SPARK-17418 > >>> > [4] https://github.com/apache/spark/pull/15167/files > >>> > > >>> > Dan > >>> > > >>> > On Tue, Oct 25, 2016 at 11:01 AM, Seetharam Venkatesh < > >>> > venkat...@innerzeal.com> wrote: > >>> > > >>> > > +1 > >>> > > > >>> > > Thanks! > >>> > > > >>> > > On Mon, Oct 24, 2016 at 2:30 PM Aljoscha Krettek > >> > >>> > > 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 > >>> > > > > >>> > > > >>> > > >>> >
Re: [VOTE] Release 0.3.0-incubating, release candidate #1
+1 (binding) Thanks for managing the release, Aljoscha! -Max On Wed, Oct 26, 2016 at 6:46 AM, Jean-Baptiste Onofré wrote: > Agree. We already discussed about that on the mailing list. I mentionned this > some weeks ago. > > Regards > JB > > > > On Oct 26, 2016, 02:26, at 02:26, Dan Halperin > wrote: >>My reading of the LEGAL threads is that since we are not including >>(shading >>or bundling) the ASL-licensed code we are fine to distribute kinesis-io >>module. This was the original conclusion that LEGAL-198 got to, and >>that >>thread has not been resolved differently (even if Spark went ahead and >>broke the assembly). The beam-sdks-java-io-kinesis module is an >>optional >>part (Beam materially works just fine without it). >> >>So I think we're fine to keep this vote open. >> >>+1 (binding) on the release >> >>Thanks Aljoscha! >> >> >>On Tue, Oct 25, 2016 at 12:07 PM, Aljoscha Krettek >> >>wrote: >> >>> Yep, I was looking at those same threads when I reviewing the >>artefacts. >>> The release was already close to being finished so I went through >>with it >>> but if we think it's not good to have them in we should quickly >>cancel in >>> favour of a new RC without a published Kinesis connector. >>> >>> On Tue, 25 Oct 2016 at 20:46 Dan Halperin >> >>> wrote: >>> >>> > I can't tell whether it is a problem that we are distributing the >>> > beam-sdks-java-io-kinesis module [0]. >>> > >>> > Here is the dev@ discussion thread [1] and the (unanswered) >>relevant >>> LEGAL >>> > thread [2]. >>> > We linked through to a Spark-related discussion [3], and here is >>how to >>> > disable distribution of the KinesisIO module [4]. >>> > >>> > [0] >>> > >>> > https://repository.apache.org/content/repositories/staging/ >>> org/apache/beam/beam-sdks-java-io-kinesis/ >>> > [1] >>> > >>> > https://lists.apache.org/thread.html/6784bc005f329d93fd59d0f8759ed4 >>> 745e72f105e39d869e094d9645@%3Cdev.beam.apache.org%3E >>> > [2] >>> > >>> > https://issues.apache.org/jira/browse/LEGAL-198? >>> focusedCommentId=15471529&page=com.atlassian.jira. >>> plugin.system.issuetabpanels:comment-tabpanel#comment-15471529 >>> > [3] https://issues.apache.org/jira/browse/SPARK-17418 >>> > [4] https://github.com/apache/spark/pull/15167/files >>> > >>> > Dan >>> > >>> > On Tue, Oct 25, 2016 at 11:01 AM, Seetharam Venkatesh < >>> > venkat...@innerzeal.com> wrote: >>> > >>> > > +1 >>> > > >>> > > Thanks! >>> > > >>> > > On Mon, Oct 24, 2016 at 2:30 PM Aljoscha Krettek >> >>> > > 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 >>> > > > >>> > > >>> > >>>
Re: [VOTE] Release 0.3.0-incubating, release candidate #1
Agree. We already discussed about that on the mailing list. I mentionned this some weeks ago. Regards JB On Oct 26, 2016, 02:26, at 02:26, Dan Halperin wrote: >My reading of the LEGAL threads is that since we are not including >(shading >or bundling) the ASL-licensed code we are fine to distribute kinesis-io >module. This was the original conclusion that LEGAL-198 got to, and >that >thread has not been resolved differently (even if Spark went ahead and >broke the assembly). The beam-sdks-java-io-kinesis module is an >optional >part (Beam materially works just fine without it). > >So I think we're fine to keep this vote open. > >+1 (binding) on the release > >Thanks Aljoscha! > > >On Tue, Oct 25, 2016 at 12:07 PM, Aljoscha Krettek > >wrote: > >> Yep, I was looking at those same threads when I reviewing the >artefacts. >> The release was already close to being finished so I went through >with it >> but if we think it's not good to have them in we should quickly >cancel in >> favour of a new RC without a published Kinesis connector. >> >> On Tue, 25 Oct 2016 at 20:46 Dan Halperin > >> wrote: >> >> > I can't tell whether it is a problem that we are distributing the >> > beam-sdks-java-io-kinesis module [0]. >> > >> > Here is the dev@ discussion thread [1] and the (unanswered) >relevant >> LEGAL >> > thread [2]. >> > We linked through to a Spark-related discussion [3], and here is >how to >> > disable distribution of the KinesisIO module [4]. >> > >> > [0] >> > >> > https://repository.apache.org/content/repositories/staging/ >> org/apache/beam/beam-sdks-java-io-kinesis/ >> > [1] >> > >> > https://lists.apache.org/thread.html/6784bc005f329d93fd59d0f8759ed4 >> 745e72f105e39d869e094d9645@%3Cdev.beam.apache.org%3E >> > [2] >> > >> > https://issues.apache.org/jira/browse/LEGAL-198? >> focusedCommentId=15471529&page=com.atlassian.jira. >> plugin.system.issuetabpanels:comment-tabpanel#comment-15471529 >> > [3] https://issues.apache.org/jira/browse/SPARK-17418 >> > [4] https://github.com/apache/spark/pull/15167/files >> > >> > Dan >> > >> > On Tue, Oct 25, 2016 at 11:01 AM, Seetharam Venkatesh < >> > venkat...@innerzeal.com> wrote: >> > >> > > +1 >> > > >> > > Thanks! >> > > >> > > On Mon, Oct 24, 2016 at 2:30 PM Aljoscha Krettek > >> > > 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 >> > > > >> > > >> > >>
Re: [VOTE] Release 0.3.0-incubating, release candidate #1
+1 (binding) On Tue, Oct 25, 2016 at 5:26 PM Dan Halperin wrote: > My reading of the LEGAL threads is that since we are not including (shading > or bundling) the ASL-licensed code we are fine to distribute kinesis-io > module. This was the original conclusion that LEGAL-198 got to, and that > thread has not been resolved differently (even if Spark went ahead and > broke the assembly). The beam-sdks-java-io-kinesis module is an optional > part (Beam materially works just fine without it). > > So I think we're fine to keep this vote open. > > +1 (binding) on the release > > Thanks Aljoscha! > > > On Tue, Oct 25, 2016 at 12:07 PM, Aljoscha Krettek > wrote: > > > Yep, I was looking at those same threads when I reviewing the artefacts. > > The release was already close to being finished so I went through with it > > but if we think it's not good to have them in we should quickly cancel in > > favour of a new RC without a published Kinesis connector. > > > > On Tue, 25 Oct 2016 at 20:46 Dan Halperin > > wrote: > > > > > I can't tell whether it is a problem that we are distributing the > > > beam-sdks-java-io-kinesis module [0]. > > > > > > Here is the dev@ discussion thread [1] and the (unanswered) relevant > > LEGAL > > > thread [2]. > > > We linked through to a Spark-related discussion [3], and here is how to > > > disable distribution of the KinesisIO module [4]. > > > > > > [0] > > > > > > https://repository.apache.org/content/repositories/staging/ > > org/apache/beam/beam-sdks-java-io-kinesis/ > > > [1] > > > > > > https://lists.apache.org/thread.html/6784bc005f329d93fd59d0f8759ed4 > > 745e72f105e39d869e094d9645@%3Cdev.beam.apache.org%3E > > > [2] > > > > > > https://issues.apache.org/jira/browse/LEGAL-198? > > focusedCommentId=15471529&page=com.atlassian.jira. > > plugin.system.issuetabpanels:comment-tabpanel#comment-15471529 > > > [3] https://issues.apache.org/jira/browse/SPARK-17418 > > > [4] https://github.com/apache/spark/pull/15167/files > > > > > > Dan > > > > > > On Tue, Oct 25, 2016 at 11:01 AM, Seetharam Venkatesh < > > > venkat...@innerzeal.com> wrote: > > > > > > > +1 > > > > > > > > Thanks! > > > > > > > > On Mon, Oct 24, 2016 at 2:30 PM Aljoscha Krettek < > aljos...@apache.org> > > > > 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 > > > > > > > > > > > > > > >
Re: [VOTE] Release 0.3.0-incubating, release candidate #1
My reading of the LEGAL threads is that since we are not including (shading or bundling) the ASL-licensed code we are fine to distribute kinesis-io module. This was the original conclusion that LEGAL-198 got to, and that thread has not been resolved differently (even if Spark went ahead and broke the assembly). The beam-sdks-java-io-kinesis module is an optional part (Beam materially works just fine without it). So I think we're fine to keep this vote open. +1 (binding) on the release Thanks Aljoscha! On Tue, Oct 25, 2016 at 12:07 PM, Aljoscha Krettek wrote: > Yep, I was looking at those same threads when I reviewing the artefacts. > The release was already close to being finished so I went through with it > but if we think it's not good to have them in we should quickly cancel in > favour of a new RC without a published Kinesis connector. > > On Tue, 25 Oct 2016 at 20:46 Dan Halperin > wrote: > > > I can't tell whether it is a problem that we are distributing the > > beam-sdks-java-io-kinesis module [0]. > > > > Here is the dev@ discussion thread [1] and the (unanswered) relevant > LEGAL > > thread [2]. > > We linked through to a Spark-related discussion [3], and here is how to > > disable distribution of the KinesisIO module [4]. > > > > [0] > > > > https://repository.apache.org/content/repositories/staging/ > org/apache/beam/beam-sdks-java-io-kinesis/ > > [1] > > > > https://lists.apache.org/thread.html/6784bc005f329d93fd59d0f8759ed4 > 745e72f105e39d869e094d9645@%3Cdev.beam.apache.org%3E > > [2] > > > > https://issues.apache.org/jira/browse/LEGAL-198? > focusedCommentId=15471529&page=com.atlassian.jira. > plugin.system.issuetabpanels:comment-tabpanel#comment-15471529 > > [3] https://issues.apache.org/jira/browse/SPARK-17418 > > [4] https://github.com/apache/spark/pull/15167/files > > > > Dan > > > > On Tue, Oct 25, 2016 at 11:01 AM, Seetharam Venkatesh < > > venkat...@innerzeal.com> wrote: > > > > > +1 > > > > > > Thanks! > > > > > > On Mon, Oct 24, 2016 at 2:30 PM Aljoscha Krettek > > > 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 > > > > > > > > > >
Re: [VOTE] Release 0.3.0-incubating, release candidate #1
Yep, I was looking at those same threads when I reviewing the artefacts. The release was already close to being finished so I went through with it but if we think it's not good to have them in we should quickly cancel in favour of a new RC without a published Kinesis connector. On Tue, 25 Oct 2016 at 20:46 Dan Halperin wrote: > I can't tell whether it is a problem that we are distributing the > beam-sdks-java-io-kinesis module [0]. > > Here is the dev@ discussion thread [1] and the (unanswered) relevant LEGAL > thread [2]. > We linked through to a Spark-related discussion [3], and here is how to > disable distribution of the KinesisIO module [4]. > > [0] > > https://repository.apache.org/content/repositories/staging/org/apache/beam/beam-sdks-java-io-kinesis/ > [1] > > https://lists.apache.org/thread.html/6784bc005f329d93fd59d0f8759ed4745e72f105e39d869e094d9645@%3Cdev.beam.apache.org%3E > [2] > > https://issues.apache.org/jira/browse/LEGAL-198?focusedCommentId=15471529&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15471529 > [3] https://issues.apache.org/jira/browse/SPARK-17418 > [4] https://github.com/apache/spark/pull/15167/files > > Dan > > On Tue, Oct 25, 2016 at 11:01 AM, Seetharam Venkatesh < > venkat...@innerzeal.com> wrote: > > > +1 > > > > Thanks! > > > > On Mon, Oct 24, 2016 at 2:30 PM Aljoscha Krettek > > 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 > > > > > >
Re: [VOTE] Release 0.3.0-incubating, release candidate #1
+1 (binding) My understanding that Kinesis licensing is not an issue since we don't redistribute that code ourselves. (I'd also be fine in excluding that code from the source distribution if deemed necessary.) On Tue, Oct 25, 2016 at 11:45 AM, Dan Halperin wrote: > I can't tell whether it is a problem that we are distributing the > beam-sdks-java-io-kinesis module [0]. > > Here is the dev@ discussion thread [1] and the (unanswered) relevant LEGAL > thread [2]. > We linked through to a Spark-related discussion [3], and here is how to > disable distribution of the KinesisIO module [4]. > > [0] > https://repository.apache.org/content/repositories/staging/ > org/apache/beam/beam-sdks-java-io-kinesis/ > [1] > https://lists.apache.org/thread.html/6784bc005f329d93fd59d0f8759ed4 > 745e72f105e39d869e094d9645@%3Cdev.beam.apache.org%3E > [2] > https://issues.apache.org/jira/browse/LEGAL-198?focusedCommentId=15471529&; > page=com.atlassian.jira.plugin.system.issuetabpanels: > comment-tabpanel#comment-15471529 > [3] https://issues.apache.org/jira/browse/SPARK-17418 > [4] https://github.com/apache/spark/pull/15167/files > > Dan > > On Tue, Oct 25, 2016 at 11:01 AM, Seetharam Venkatesh < > venkat...@innerzeal.com> wrote: > > > +1 > > > > Thanks! > > > > On Mon, Oct 24, 2016 at 2:30 PM Aljoscha Krettek > > 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 > > > > > >
Re: [VOTE] Release 0.3.0-incubating, release candidate #1
I can't tell whether it is a problem that we are distributing the beam-sdks-java-io-kinesis module [0]. Here is the dev@ discussion thread [1] and the (unanswered) relevant LEGAL thread [2]. We linked through to a Spark-related discussion [3], and here is how to disable distribution of the KinesisIO module [4]. [0] https://repository.apache.org/content/repositories/staging/org/apache/beam/beam-sdks-java-io-kinesis/ [1] https://lists.apache.org/thread.html/6784bc005f329d93fd59d0f8759ed4745e72f105e39d869e094d9645@%3Cdev.beam.apache.org%3E [2] https://issues.apache.org/jira/browse/LEGAL-198?focusedCommentId=15471529&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15471529 [3] https://issues.apache.org/jira/browse/SPARK-17418 [4] https://github.com/apache/spark/pull/15167/files Dan On Tue, Oct 25, 2016 at 11:01 AM, Seetharam Venkatesh < venkat...@innerzeal.com> wrote: > +1 > > Thanks! > > On Mon, Oct 24, 2016 at 2:30 PM Aljoscha Krettek > 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 > > >
Re: [VOTE] Release 0.3.0-incubating, release candidate #1
+1 Thanks! On Mon, Oct 24, 2016 at 2:30 PM Aljoscha Krettek 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 >
Re: [VOTE] Release 0.3.0-incubating, release candidate #1
Thanks Sergio ;) Just tried to explain to the others what is a binding vote ;) Regards JB On Oct 25, 2016, 11:53, at 11:53, "Sergio Fernández" wrote: >On Tue, Oct 25, 2016 at 11:36 AM, Jean-Baptiste Onofré > >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" > >> 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 >> > >> >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 >> >e: sergio.fernan...@redlink.co >> >w: http://redlink.co >> > > > >-- >Sergio Fernández >Partner Technology Manager >Redlink GmbH >m: +43 6602747925 >e: sergio.fernan...@redlink.co >w: http://redlink.co
Re: [VOTE] Release 0.3.0-incubating, release candidate #1
Imho it's better to use md5sun/sha1sum. About mongodb I will implement a free port use to avoid the failing test if an existing instance is already running locally. Regards JB On Oct 25, 2016, 12:07, at 12:07, Aljoscha Krettek wrote: >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 >wrote: > >> On Tue, Oct 25, 2016 at 11:36 AM, Jean-Baptiste Onofré > >> 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" > >> > 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 >> > > >> > >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: sergio.fernan...@redlink.co >> > >w: http://redlink.co >> > >> >> >> >> -- >> Sergio Fernández >> Partner Technology Manager >> Redlink GmbH >> m: +43 6602747925 <+43%20660%202747925> >> e: sergio.fernan...@redlink.co >> w: http://redlink.co >>
Re: [VOTE] Release 0.3.0-incubating, release candidate #1
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 wrote: > On Tue, Oct 25, 2016 at 11:36 AM, Jean-Baptiste Onofré > 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" > > 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 > > > > > >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: sergio.fernan...@redlink.co > > >w: http://redlink.co > > > > > > -- > Sergio Fernández > Partner Technology Manager > Redlink GmbH > m: +43 6602747925 <+43%20660%202747925> > e: sergio.fernan...@redlink.co > w: http://redlink.co >
Re: [VOTE] Release 0.3.0-incubating, release candidate #1
On Tue, Oct 25, 2016 at 11:36 AM, Jean-Baptiste Onofré 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" > 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 > > > >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 > >e: sergio.fernan...@redlink.co > >w: http://redlink.co > -- Sergio Fernández Partner Technology Manager Redlink GmbH m: +43 6602747925 e: sergio.fernan...@redlink.co w: http://redlink.co
Re: [VOTE] Release 0.3.0-incubating, release candidate #1
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). So this vote is +1 (non binding). Regards JB On Oct 25, 2016, 11:33, at 11:33, "Sergio Fernández" 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 > >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 >e: sergio.fernan...@redlink.co >w: http://redlink.co
Re: [VOTE] Release 0.3.0-incubating, release candidate #1
+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 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 e: sergio.fernan...@redlink.co w: http://redlink.co
Re: [VOTE] Release 0.3.0-incubating, release candidate #1
It's actually mentionned on the incubator thread usually. Regards JB On Oct 25, 2016, 09:46, at 09:46, "Ismaël Mejía" wrote: >+1 (non-binding) > >- verified signatures + checksums >- run mvn clean verify, all artifacts+tests run successfully > >One thing to add for future vote calls [idea copied from the latest >flink >vote ;)]: > >The release artifacts are signed with the key with fingerprint 121D7293 >https://dist.apache.org/repos/dist/release/incubator/beam/KEYS > > > >On Tue, Oct 25, 2016 at 7:55 AM, Jean-Baptiste Onofré >wrote: > >> +1 (binding) >> >> I did a quick review and tests. It looks good to me. >> >> Regards >> JB >> >> >> >> On Oct 24, 2016, 23:30, at 23:30, Aljoscha Krettek > >> 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 >>
Re: [VOTE] Release 0.3.0-incubating, release candidate #1
+1 (non-binding) - verified signatures + checksums - run mvn clean verify, all artifacts+tests run successfully One thing to add for future vote calls [idea copied from the latest flink vote ;)]: The release artifacts are signed with the key with fingerprint 121D7293 https://dist.apache.org/repos/dist/release/incubator/beam/KEYS On Tue, Oct 25, 2016 at 7:55 AM, Jean-Baptiste Onofré wrote: > +1 (binding) > > I did a quick review and tests. It looks good to me. > > Regards > JB > > > > On Oct 24, 2016, 23:30, at 23:30, Aljoscha Krettek > 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 >
Re: [VOTE] Release 0.3.0-incubating, release candidate #1
+1 (binding) I did a quick review and tests. It looks good to me. Regards JB On Oct 24, 2016, 23:30, at 23:30, Aljoscha Krettek 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