Re: [VOTE] Apache Beam, version 2.5.0, release candidate #2

+1, Thank you JB. JB, python wheel files are not included in https://dist.apache.org/repos/ dist/dev/beam/2.5.0/. Since Yifan already validated the wheels files built by Boyuan, could you copy those files to the release folder before closing the vote? On Wed, Jun 20, 2018 at 1:19 PM, Pablo

Re: Broken links to releases

We can also just link to https://beam.apache.org/get-started/downloads/ and ask users to download the corresponding/latest release. On Wed, Jun 20, 2018 at 9:13 AM Robert Bradshaw wrote: > So when we send out announcements, etc. we should be linking to > archive.apache.org so as not to break

Re: [VOTE] Apache Beam, version 2.5.0, release candidate #2

Since we use git-published archives to push to dist.apache.org, we only need to add an exclusion of those files in .gitattributes. Here's the PR to fix that: https://github.com/apache/beam/pull/5699 Here's an example of a published archive from the branch with that exclusion:

Re: Proposal for Beam Python User State and Timer APIs

An update on the implementation: I recently sent out the user-facing pipeline construction part of the API implementation out for review: https://github.com/apache/beam/pull/5691. On Tue, Jun 5, 2018 at 5:26 PM Charles Chen wrote: > Thanks everyone for contributing here. We've reached rough

Re: [VOTE] Apache Beam, version 2.5.0, release candidate #2

Sorry, no -1, at least not at this time. This is only a suspected issue. Even the referenced issue is not a formal ruling, with some dissenting opinions, and a programatic suggestion that most are comfortable with. (Personally, I probably lean on the side that inclusion of this file is fine.)

Re: [VOTE] Apache Beam, version 2.5.0, release candidate #2

I had a chance to look closely. Bringing some details to this thread. We have the following Apache 2.0 licensed files in our source release zip: beam-release-2.5.0/gradle.properties beam-release-2.5.0/gradle/ beam-release-2.5.0/gradle/wrapper/

Re: Broken links to releases

Removing the pre-2.x releases sounds like a good idea. On Wed, Jun 20, 2018 at 11:52 AM Thomas Weise wrote: > As a related question, what are the thoughts on removing pre 2.x releases > from that page? > > > On Wed, Jun 20, 2018 at 6:16 PM, Chamikara Jayalath > wrote: > >> We can also just

Re: [VOTE] Apache Beam, version 2.5.0, release candidate #2

+1 (binding) On Wed, Jun 20, 2018 at 9:08 AM Lukasz Cwik wrote: > +1 (binding) > > On Tue, Jun 19, 2018 at 10:39 PM Jean-Baptiste Onofré > wrote: > >> +1 (binding) >> >> Regards >> JB >> >> On 17/06/2018 07:18, Jean-Baptiste Onofré wrote: >> > Hi everyone, >> > >> > Please review and vote on

Re: [VOTE] Apache Beam, version 2.5.0, release candidate #2

Please take a peek at LEGAL-288 [1], which I learned about recently in the context of another project. Looks like an issue, requiring a new RC, but I didn't have a chance to look closely. Thanks. Davor [1] https://issues.apache.org/jira/browse/LEGAL-288 On Wed, Jun 20, 2018 at 9:17 AM, Pablo

Re: [VOTE] Apache Beam, version 2.5.0, release candidate #2

Davor, please -1 the release if you believe LEGAL-288 applies. On Wed, Jun 20, 2018 at 9:37 AM Davor Bonaci wrote: > Please take a peek at LEGAL-288 [1], which I learned about recently in the > context of another project. Looks like an issue, requiring a new RC, but I > didn't have a chance to

Re: Broken links to releases

So when we send out announcements, etc. we should be linking to archive.apache.org so as not to break them in the future then. I suppose we could add another manual step to change the links for old releases on the website when we do new releases (though the less work to give the release manager

Re: Broken links to releases

As a related question, what are the thoughts on removing pre 2.x releases from that page? On Wed, Jun 20, 2018 at 6:16 PM, Chamikara Jayalath wrote: > We can also just link to https://beam.apache.org/get-started/downloads/ > and ask users to download the corresponding/latest release. > > > On

Re: Broken links to releases

+1 to removing pre-2.x releases from the page On Wed, Jun 20, 2018 at 12:24 PM Lukasz Cwik wrote: > Removing the pre-2.x releases sounds like a good idea. > > On Wed, Jun 20, 2018 at 11:52 AM Thomas Weise wrote: > >> As a related question, what are the thoughts on removing pre 2.x releases >>

Re: [FYI] New Apache Beam Swag Store!

Hey Robert, I have requested to include this in the webshop or send me the sizes via e-mail. I'll let you know if I get an update on this! Cheers, Matthias On Thu, 14 Jun 2018 at 23:22 Robert Burke wrote: > Would it be possible to get the brand of the shirts & sweaters, and the > sizing

Re: [VOTE] Apache Beam, version 2.5.0, release candidate #2

I support Kenn's proposal of removing binary artifacts and otherwise keeping the RC2. We have done it in the pas with similar binary files that were unintended. At the same time, it will follow the suggestion from LEGAL-288. As a follow up we can build this removal into our release process until

Re: [VOTE] Apache Beam, version 2.5.0, release candidate #2

+1 (binding) On Tue, Jun 19, 2018 at 10:39 PM Jean-Baptiste Onofré wrote: > +1 (binding) > > Regards > JB > > On 17/06/2018 07:18, Jean-Baptiste Onofré wrote: > > Hi everyone, > > > > Please review and vote on the release candidate #2 for the version > > 2.5.0, as follows: > > > > [ ] +1,

Re: [VOTE] Apache Beam, version 2.5.0, release candidate #2

SGTM, if its just dropping gradle-wrapper.jar file from the source zip. On Wed, Jun 20, 2018 at 10:47 AM Kenneth Knowles wrote: > I had a chance to look closely. Bringing some details to this thread. > > We have the following Apache 2.0 licensed files in our source release zip: > >

Re: [FYI] New Apache Beam Swag Store!

Thank you Matthias! On Wed, Jun 20, 2018, 1:09 AM Matthias Baetens wrote: > Hey Robert, > > I have requested to include this in the webshop or send me the sizes via > e-mail. I'll let you know if I get an update on this! > > Cheers, > Matthias > > On Thu, 14 Jun 2018 at 23:22 Robert Burke

Re: Python Development Environments for Apache Beam

Do you happen to have a tweet we reshould RT for reach? On Wed, Jun 20, 2018, 11:26 AM Josh McGinley wrote: > Beam Users and Dev - > > I recently published a medium article >