Re: [FYI] New Apache Beam Swag Store!

[Matthias Baetens]

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 information? The vendor should have that available. The pages have a
> lot of fabric and cut description, but not the measurements.
> Sizes fit varies dramatically on the brand, and if I get a hoodie,
> anything from a Medium to and XL can fit my arms and torso properly.
>
> On Wed, 13 Jun 2018 at 11:10 Griselda Cuevas  wrote:
>
>> Thanks All!
>>
>> To close the loop on the suggestions, I'll order more t-shirts in black
>> so we have some options.
>>
>> G
>>
>> On Wed, 13 Jun 2018 at 08:39, Ismaël Mejía  wrote:
>>
>>> Great ! Thanks Gris and Matthias for putting this in place.
>>> Hope to get that hoodie soon. As a suggestion, more colors too, and
>>> eventually a t-shirt just with the big B logo.
>>> On Mon, Jun 11, 2018 at 6:50 PM Mikhail Gryzykhin 
>>> wrote:
>>> >
>>> > That's nice!
>>> >
>>> > More colors are appreciated :)
>>> >
>>> > --Mikhail
>>> >
>>> >
>>> > On Sun, Jun 10, 2018 at 8:20 PM Kenneth Knowles 
>>> wrote:
>>> >>
>>> >> Sweet! Agree with Raghu :-)
>>> >>
>>> >> Kenn
>>> >>
>>> >> On Sun, Jun 10, 2018 at 6:06 AM Matthias Baetens <
>>> baetensmatth...@gmail.com> wrote:
>>> >>>
>>> >>> Great news, big thanks for all the work, Gris! Looking forward to
>>> people wearing this around the globe ;)
>>> >>>
>>> >>> On Sat, 9 Jun 2018 at 01:28 Ankur Goenka  wrote:
>>> 
>>>  Awesome!
>>> 
>>> 
>>>  On Fri, Jun 8, 2018 at 4:24 PM Pablo Estrada 
>>> wrote:
>>> >
>>> > Nice : D
>>> >
>>> > On Fri, Jun 8, 2018, 3:43 PM Raghu Angadi 
>>> wrote:
>>> >>
>>> >> Woo-hoo! This is terrific.
>>> >>
>>> >> If we are increasing color choices I would like black or
>>> charcoal... Beam logo would really pop on a dark background.
>>> >>
>>> >> On Fri, Jun 8, 2018 at 3:32 PM Griselda Cuevas 
>>> wrote:
>>> >>>
>>> >>> Hi Beam Community,
>>> >>>
>>> >>> I just want to share with you the exciting news about our brand
>>> new Apache Beam Swag Store!
>>> >>>
>>> >>> You can find it here: https://store-beam.myshopify.com/
>>> >>>
>>> >>> How does it work?
>>> >>>
>>> >>> You can just select the items you want and check-out. Our Vendor
>>> ships to anywhere in the world and normally can have swag to be delivered
>>> within 1 week. Each company or user will need to pay for their own swag.
>>> >>> If you are hosting an event or representing Beam at one, reach
>>> out to me or the beam-events-meetups slack channel, I'll be happy to review
>>> your event and see if we can sponsor the swag. We'll have codes for this
>>> occasions thanks to Google, who has sponsored an initial inventory.
>>> >>>
>>> >>> If you have feedback, ideas on new swag, questions or
>>> suggestions, reach out to me and/or Matthias Baetens.
>>> >>>
>>> >>> Happy Friday!
>>> >>> G
>>> >>>
>>> >>>
>>> > --
>>> > Got feedback? go/pabloem-feedback
>>> 
>>> >>>
>>> >>> --
>>> >>>
>>>
>> --

Re: [FYI] New Apache Beam Swag Store!

[Robert Burke]

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  wrote:
>
>> Would it be possible to get the brand of the shirts & sweaters, and the
>> sizing information? The vendor should have that available. The pages have a
>> lot of fabric and cut description, but not the measurements.
>> Sizes fit varies dramatically on the brand, and if I get a hoodie,
>> anything from a Medium to and XL can fit my arms and torso properly.
>>
>> On Wed, 13 Jun 2018 at 11:10 Griselda Cuevas  wrote:
>>
>>> Thanks All!
>>>
>>> To close the loop on the suggestions, I'll order more t-shirts in black
>>> so we have some options.
>>>
>>> G
>>>
>>> On Wed, 13 Jun 2018 at 08:39, Ismaël Mejía  wrote:
>>>
 Great ! Thanks Gris and Matthias for putting this in place.
 Hope to get that hoodie soon. As a suggestion, more colors too, and
 eventually a t-shirt just with the big B logo.
 On Mon, Jun 11, 2018 at 6:50 PM Mikhail Gryzykhin 
 wrote:
 >
 > That's nice!
 >
 > More colors are appreciated :)
 >
 > --Mikhail
 >
 >
 > On Sun, Jun 10, 2018 at 8:20 PM Kenneth Knowles 
 wrote:
 >>
 >> Sweet! Agree with Raghu :-)
 >>
 >> Kenn
 >>
 >> On Sun, Jun 10, 2018 at 6:06 AM Matthias Baetens <
 baetensmatth...@gmail.com> wrote:
 >>>
 >>> Great news, big thanks for all the work, Gris! Looking forward to
 people wearing this around the globe ;)
 >>>
 >>> On Sat, 9 Jun 2018 at 01:28 Ankur Goenka  wrote:
 
  Awesome!
 
 
  On Fri, Jun 8, 2018 at 4:24 PM Pablo Estrada 
 wrote:
 >
 > Nice : D
 >
 > On Fri, Jun 8, 2018, 3:43 PM Raghu Angadi 
 wrote:
 >>
 >> Woo-hoo! This is terrific.
 >>
 >> If we are increasing color choices I would like black or
 charcoal... Beam logo would really pop on a dark background.
 >>
 >> On Fri, Jun 8, 2018 at 3:32 PM Griselda Cuevas 
 wrote:
 >>>
 >>> Hi Beam Community,
 >>>
 >>> I just want to share with you the exciting news about our brand
 new Apache Beam Swag Store!
 >>>
 >>> You can find it here: https://store-beam.myshopify.com/
 >>>
 >>> How does it work?
 >>>
 >>> You can just select the items you want and check-out. Our
 Vendor ships to anywhere in the world and normally can have swag to be
 delivered within 1 week. Each company or user will need to pay for their
 own swag.
 >>> If you are hosting an event or representing Beam at one, reach
 out to me or the beam-events-meetups slack channel, I'll be happy to review
 your event and see if we can sponsor the swag. We'll have codes for this
 occasions thanks to Google, who has sponsored an initial inventory.
 >>>
 >>> If you have feedback, ideas on new swag, questions or
 suggestions, reach out to me and/or Matthias Baetens.
 >>>
 >>> Happy Friday!
 >>> G
 >>>
 >>>
 > --
 > Got feedback? go/pabloem-feedback
 
 >>>
 >>> --
 >>>

>>> --
>
>

Re: Python Development Environments for Apache Beam

[Holden Karau]

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
> 
>  showing how to set up Python Apache Beam pipelines for debugging in an
> IDE.
>
> I thought I would share the article with this community.  If you have any
> feedback let me know.  Otherwise keep up the great work on Beam!
>
> --
> Josh McGinley
>

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

[Lukasz Cwik]

+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, Approve the release
> > [ ] -1, Do not approve the release (please provide specific comments)
> >
> > NB: this is the first release using Gradle, so don't be too harsh ;) A
> > PR about the release guide will follow thanks to this release.
> >
> > 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], which is signed with the key with fingerprint C8282E76 [3],
> > * all artifacts to be deployed to the Maven Central Repository [4],
> > * source code tag "v2.5.0-RC2" [5],
> > * website pull request listing the release and publishing the API
> > reference manual [6].
> > * Java artifacts were built with Gradle 4.7 (wrapper) and OpenJDK/Oracle
> > JDK 1.8.0_172 (Oracle Corporation 25.172-b11).
> > * Python artifacts are deployed along with the source release to the
> > dist.apache.org [2].
> >
> > The vote will be open for at least 72 hours. It is adopted by majority
> > approval, with at least 3 PMC affirmative votes.
> >
> > Thanks,
> > JB
> >
> > [1]
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527&version=12342847
> > [2] https://dist.apache.org/repos/dist/dev/beam/2.5.0/
> > [3] https://dist.apache.org/repos/dist/release/beam/KEYS
> > [4]
> https://repository.apache.org/content/repositories/orgapachebeam-1043/
> > [5] https://github.com/apache/beam/tree/v2.5.0-RC2
> > [6] https://github.com/apache/beam-site/pull/463
> >
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: Broken links to releases

[Robert Bradshaw]

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 the better).

Re: Broken links to releases

[Chamikara Jayalath]

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 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 the better).
>

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

[Pablo Estrada]

+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 the release candidate #2 for the version
>> > 2.5.0, as follows:
>> >
>> > [ ] +1, Approve the release
>> > [ ] -1, Do not approve the release (please provide specific comments)
>> >
>> > NB: this is the first release using Gradle, so don't be too harsh ;) A
>> > PR about the release guide will follow thanks to this release.
>> >
>> > 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], which is signed with the key with fingerprint C8282E76 [3],
>> > * all artifacts to be deployed to the Maven Central Repository [4],
>> > * source code tag "v2.5.0-RC2" [5],
>> > * website pull request listing the release and publishing the API
>> > reference manual [6].
>> > * Java artifacts were built with Gradle 4.7 (wrapper) and OpenJDK/Oracle
>> > JDK 1.8.0_172 (Oracle Corporation 25.172-b11).
>> > * Python artifacts are deployed along with the source release to the
>> > dist.apache.org [2].
>> >
>> > The vote will be open for at least 72 hours. It is adopted by majority
>> > approval, with at least 3 PMC affirmative votes.
>> >
>> > Thanks,
>> > JB
>> >
>> > [1]
>> >
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527&version=12342847
>> > [2] https://dist.apache.org/repos/dist/dev/beam/2.5.0/
>> > [3] https://dist.apache.org/repos/dist/release/beam/KEYS
>> > [4]
>> https://repository.apache.org/content/repositories/orgapachebeam-1043/
>> > [5] https://github.com/apache/beam/tree/v2.5.0-RC2
>> > [6] https://github.com/apache/beam-site/pull/463
>> >
>>
>> --
>> Jean-Baptiste Onofré
>> jbono...@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
> --
Got feedback? go/pabloem-feedback

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

[Davor Bonaci]

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 Estrada  wrote:

> +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 the release candidate #2 for the version
>>> > 2.5.0, as follows:
>>> >
>>> > [ ] +1, Approve the release
>>> > [ ] -1, Do not approve the release (please provide specific comments)
>>> >
>>> > NB: this is the first release using Gradle, so don't be too harsh ;) A
>>> > PR about the release guide will follow thanks to this release.
>>> >
>>> > 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], which is signed with the key with fingerprint C8282E76 [3],
>>> > * all artifacts to be deployed to the Maven Central Repository [4],
>>> > * source code tag "v2.5.0-RC2" [5],
>>> > * website pull request listing the release and publishing the API
>>> > reference manual [6].
>>> > * Java artifacts were built with Gradle 4.7 (wrapper) and
>>> OpenJDK/Oracle
>>> > JDK 1.8.0_172 (Oracle Corporation 25.172-b11).
>>> > * Python artifacts are deployed along with the source release to the
>>> > dist.apache.org [2].
>>> >
>>> > The vote will be open for at least 72 hours. It is adopted by majority
>>> > approval, with at least 3 PMC affirmative votes.
>>> >
>>> > Thanks,
>>> > JB
>>> >
>>> > [1]
>>> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
>>> projectId=12319527&version=12342847
>>> > [2] https://dist.apache.org/repos/dist/dev/beam/2.5.0/
>>> > [3] https://dist.apache.org/repos/dist/release/beam/KEYS
>>> > [4] https://repository.apache.org/content/repositories/
>>> orgapachebeam-1043/
>>> > [5] https://github.com/apache/beam/tree/v2.5.0-RC2
>>> > [6] https://github.com/apache/beam-site/pull/463
>>> >
>>>
>>> --
>>> Jean-Baptiste Onofré
>>> jbono...@apache.org
>>> http://blog.nanthrax.net
>>> Talend - http://www.talend.com
>>>
>> --
> Got feedback? go/pabloem-feedback
>

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

[Lukasz Cwik]

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 look closely.
>
> Thanks.
>
> Davor
>
> [1] https://issues.apache.org/jira/browse/LEGAL-288
>
> On Wed, Jun 20, 2018 at 9:17 AM, Pablo Estrada  wrote:
>
>> +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 the release candidate #2 for the version
 > 2.5.0, as follows:
 >
 > [ ] +1, Approve the release
 > [ ] -1, Do not approve the release (please provide specific comments)
 >
 > NB: this is the first release using Gradle, so don't be too harsh ;) A
 > PR about the release guide will follow thanks to this release.
 >
 > 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], which is signed with the key with fingerprint C8282E76 [3],
 > * all artifacts to be deployed to the Maven Central Repository [4],
 > * source code tag "v2.5.0-RC2" [5],
 > * website pull request listing the release and publishing the API
 > reference manual [6].
 > * Java artifacts were built with Gradle 4.7 (wrapper) and
 OpenJDK/Oracle
 > JDK 1.8.0_172 (Oracle Corporation 25.172-b11).
 > * Python artifacts are deployed along with the source release to the
 > dist.apache.org [2].
 >
 > The vote will be open for at least 72 hours. It is adopted by majority
 > approval, with at least 3 PMC affirmative votes.
 >
 > Thanks,
 > JB
 >
 > [1]
 >
 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527&version=12342847
 > [2] https://dist.apache.org/repos/dist/dev/beam/2.5.0/
 > [3] https://dist.apache.org/repos/dist/release/beam/KEYS
 > [4]
 https://repository.apache.org/content/repositories/orgapachebeam-1043/
 > [5] https://github.com/apache/beam/tree/v2.5.0-RC2
 > [6] https://github.com/apache/beam-site/pull/463
 >

 --
 Jean-Baptiste Onofré
 jbono...@apache.org
 http://blog.nanthrax.net
 Talend - http://www.talend.com

>>> --
>> Got feedback? go/pabloem-feedback
>> 
>>
>
>

Re: Proposal for Beam Python User State and Timer APIs

[Charles Chen]

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 consensus on
> the approach we should take with this API, and I've summarized this in the
> new "Community consensus" sections I added to the doc (
> https://s.apache.org/beam-python-user-state-and-timers).  I will begin
> initial implementation of this API soon.
>
> On Wed, May 23, 2018 at 8:08 PM Thomas Weise  wrote:
>
>> Nice proposal; it's exciting to see this about to be added to the SDK as
>> it enables a set of more complex use cases.
>>
>> I also think that some of the content can later be repurposed as user
>> documentation.
>>
>> Thanks,
>> Thomas
>>
>>
>> On Wed, May 23, 2018 at 11:49 AM, Charles Chen  wrote:
>>
>>> Thanks everyone for the detailed comments and discussions.  It looks
>>> like by now, we mostly agree with the requirements and overall direction
>>> needed for the API, though there is continuing discussion on specific
>>> details.  I want to highlight two new sections of the doc, which address
>>> some discussions that have come up:
>>>
>>>- *Existing state and transactionality*: this section addresses how
>>>we will address an existing transactionality inconsistency in the 
>>> existing
>>>Java API.  (
>>>
>>> https://docs.google.com/document/d/1GadEkAmtbJQjmqiqfSzGw3b66TKerm8tyn6TK4blAys/edit#heading=h.ofyl9jspiz3b
>>>)
>>>- *State for merging windows*: this section addresses how we will
>>>deal with non-combinable state in conjunction with merging windows.  (
>>>
>>> https://docs.google.com/document/d/1GadEkAmtbJQjmqiqfSzGw3b66TKerm8tyn6TK4blAys/edit#heading=h.ctxkcgabtzpy
>>>)
>>>
>>> Let me know any further comments and suggestions.
>>>
>>> On Tue, May 22, 2018 at 9:29 AM Kenneth Knowles  wrote:
>>>
 Nice. I know that Java users have found it helpful to have this
 lower-level way of writing pipelines when the high-level primitives don't
 quite have the tight control they are looking for. I hope it will be a big
 draw for Python, too.

 (commenting on the doc)

 Kenn

 On Mon, May 21, 2018 at 5:15 PM Charles Chen  wrote:

> I want to share a proposal for adding user state and timer support to
> the Beam Python SDK and get the community's thoughts on how such an API
> should look: https://s.apache.org/beam-python-user-state-and-timers
>
> Let me know what you think and please add any comments and suggestions
> you may have.
>
> Best,
> Charles
>

>>

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

[Davor Bonaci]

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.)

But, it is something that warrants a discussion...

On Wed, Jun 20, 2018 at 9:47 AM, Lukasz Cwik  wrote:

> 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 look closely.
>>
>> Thanks.
>>
>> Davor
>>
>> [1] https://issues.apache.org/jira/browse/LEGAL-288
>>
>> On Wed, Jun 20, 2018 at 9:17 AM, Pablo Estrada 
>> wrote:
>>
>>> +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 the release candidate #2 for the version
> > 2.5.0, as follows:
> >
> > [ ] +1, Approve the release
> > [ ] -1, Do not approve the release (please provide specific comments)
> >
> > NB: this is the first release using Gradle, so don't be too harsh ;)
> A
> > PR about the release guide will follow thanks to this release.
> >
> > 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], which is signed with the key with fingerprint C8282E76 [3],
> > * all artifacts to be deployed to the Maven Central Repository [4],
> > * source code tag "v2.5.0-RC2" [5],
> > * website pull request listing the release and publishing the API
> > reference manual [6].
> > * Java artifacts were built with Gradle 4.7 (wrapper) and
> OpenJDK/Oracle
> > JDK 1.8.0_172 (Oracle Corporation 25.172-b11).
> > * Python artifacts are deployed along with the source release to the
> > dist.apache.org [2].
> >
> > The vote will be open for at least 72 hours. It is adopted by
> majority
> > approval, with at least 3 PMC affirmative votes.
> >
> > Thanks,
> > JB
> >
> > [1]
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje
> ctId=12319527&version=12342847
> > [2] https://dist.apache.org/repos/dist/dev/beam/2.5.0/
> > [3] https://dist.apache.org/repos/dist/release/beam/KEYS
> > [4] https://repository.apache.org/content/repositories/orgapache
> beam-1043/
> > [5] https://github.com/apache/beam/tree/v2.5.0-RC2
> > [6] https://github.com/apache/beam-site/pull/463
> >
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
 --
>>> Got feedback? go/pabloem-feedback
>>> 
>>>
>>
>>

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

[Kenneth Knowles]

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/
beam-release-2.5.0/gradle/wrapper/gradle-wrapper.jar
beam-release-2.5.0/gradle/wrapper/gradle-wrapper.properties
beam-release-2.5.0/gradlew
beam-release-2.5.0/gradlew.bat

LEGAL-288 is unresolved, but looks like the mostly likely result is that we
must remove gradle-wrapper.jar. This matches ASF policy about putting any
binary artifact in the source zip. Apache Fineract is one place we could
look for an example of doing exactly this.

In the past, we have manually tweaked the zip to remove extraneous files
without rolling a new RC & vote. Can do that here, since the release has
been thoroughly vetted?

Kenn

On Wed, Jun 20, 2018 at 10:25 AM Davor Bonaci  wrote:

> 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.)
>
> But, it is something that warrants a discussion...
>
> On Wed, Jun 20, 2018 at 9:47 AM, Lukasz Cwik  wrote:
>
>> 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 look closely.
>>>
>>> Thanks.
>>>
>>> Davor
>>>
>>> [1] https://issues.apache.org/jira/browse/LEGAL-288
>>>
>>> On Wed, Jun 20, 2018 at 9:17 AM, Pablo Estrada 
>>> wrote:
>>>
 +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 the release candidate #2 for the version
>> > 2.5.0, as follows:
>> >
>> > [ ] +1, Approve the release
>> > [ ] -1, Do not approve the release (please provide specific
>> comments)
>> >
>> > NB: this is the first release using Gradle, so don't be too harsh
>> ;) A
>> > PR about the release guide will follow thanks to this release.
>> >
>> > 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], which is signed with the key with fingerprint C8282E76 [3],
>> > * all artifacts to be deployed to the Maven Central Repository [4],
>> > * source code tag "v2.5.0-RC2" [5],
>> > * website pull request listing the release and publishing the API
>> > reference manual [6].
>> > * Java artifacts were built with Gradle 4.7 (wrapper) and
>> OpenJDK/Oracle
>> > JDK 1.8.0_172 (Oracle Corporation 25.172-b11).
>> > * Python artifacts are deployed along with the source release to the
>> > dist.apache.org [2].
>> >
>> > The vote will be open for at least 72 hours. It is adopted by
>> majority
>> > approval, with at least 3 PMC affirmative votes.
>> >
>> > Thanks,
>> > JB
>> >
>> > [1]
>> >
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527&version=12342847
>> > [2] https://dist.apache.org/repos/dist/dev/beam/2.5.0/
>> > [3] https://dist.apache.org/repos/dist/release/beam/KEYS
>> > [4]
>> https://repository.apache.org/content/repositories/orgapachebeam-1043/
>> > [5] https://github.com/apache/beam/tree/v2.5.0-RC2
>> > [6] https://github.com/apache/beam-site/pull/463
>> >
>>
>> --
>> Jean-Baptiste Onofré
>> jbono...@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
> --
 Got feedback? go/pabloem-feedback
 

>>>
>>>
>

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

[Lukasz Cwik]

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:
>
> beam-release-2.5.0/gradle.properties
> beam-release-2.5.0/gradle/
> beam-release-2.5.0/gradle/wrapper/
> beam-release-2.5.0/gradle/wrapper/gradle-wrapper.jar
> beam-release-2.5.0/gradle/wrapper/gradle-wrapper.properties
> beam-release-2.5.0/gradlew
> beam-release-2.5.0/gradlew.bat
>
> LEGAL-288 is unresolved, but looks like the mostly likely result is that
> we must remove gradle-wrapper.jar. This matches ASF policy about putting
> any binary artifact in the source zip. Apache Fineract is one place we
> could look for an example of doing exactly this.
>
> In the past, we have manually tweaked the zip to remove extraneous files
> without rolling a new RC & vote. Can do that here, since the release has
> been thoroughly vetted?
>
> Kenn
>
> On Wed, Jun 20, 2018 at 10:25 AM Davor Bonaci  wrote:
>
>> 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.)
>>
>> But, it is something that warrants a discussion...
>>
>> On Wed, Jun 20, 2018 at 9:47 AM, Lukasz Cwik  wrote:
>>
>>> 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 look closely.

 Thanks.

 Davor

 [1] https://issues.apache.org/jira/browse/LEGAL-288

 On Wed, Jun 20, 2018 at 9:17 AM, Pablo Estrada 
 wrote:

> +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é <
>> j...@nanthrax.net> 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, Approve the release
>>> > [ ] -1, Do not approve the release (please provide specific
>>> comments)
>>> >
>>> > NB: this is the first release using Gradle, so don't be too harsh
>>> ;) A
>>> > PR about the release guide will follow thanks to this release.
>>> >
>>> > 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], which is signed with the key with fingerprint C8282E76 [3],
>>> > * all artifacts to be deployed to the Maven Central Repository [4],
>>> > * source code tag "v2.5.0-RC2" [5],
>>> > * website pull request listing the release and publishing the API
>>> > reference manual [6].
>>> > * Java artifacts were built with Gradle 4.7 (wrapper) and
>>> OpenJDK/Oracle
>>> > JDK 1.8.0_172 (Oracle Corporation 25.172-b11).
>>> > * Python artifacts are deployed along with the source release to
>>> the
>>> > dist.apache.org [2].
>>> >
>>> > The vote will be open for at least 72 hours. It is adopted by
>>> majority
>>> > approval, with at least 3 PMC affirmative votes.
>>> >
>>> > Thanks,
>>> > JB
>>> >
>>> > [1]
>>> >
>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527&version=12342847
>>> > [2] https://dist.apache.org/repos/dist/dev/beam/2.5.0/
>>> > [3] https://dist.apache.org/repos/dist/release/beam/KEYS
>>> > [4]
>>> https://repository.apache.org/content/repositories/orgapachebeam-1043/
>>> > [5] https://github.com/apache/beam/tree/v2.5.0-RC2
>>> > [6] https://github.com/apache/beam-site/pull/463
>>> >
>>>
>>> --
>>> Jean-Baptiste Onofré
>>> jbono...@apache.org
>>> http://blog.nanthrax.net
>>> Talend - http://www.talend.com
>>>
>> --
> Got feedback? go/pabloem-feedback
> 
>


>>

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

[Ahmet Altay]

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 there is a resolution to the issue.

Ahmet

On Wed, Jun 20, 2018 at 10:46 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:
>
> beam-release-2.5.0/gradle.properties
> beam-release-2.5.0/gradle/
> beam-release-2.5.0/gradle/wrapper/
> beam-release-2.5.0/gradle/wrapper/gradle-wrapper.jar
> beam-release-2.5.0/gradle/wrapper/gradle-wrapper.properties
> beam-release-2.5.0/gradlew
> beam-release-2.5.0/gradlew.bat
>
> LEGAL-288 is unresolved, but looks like the mostly likely result is that
> we must remove gradle-wrapper.jar. This matches ASF policy about putting
> any binary artifact in the source zip. Apache Fineract is one place we
> could look for an example of doing exactly this.
>
> In the past, we have manually tweaked the zip to remove extraneous files
> without rolling a new RC & vote. Can do that here, since the release has
> been thoroughly vetted?
>
> Kenn
>
> On Wed, Jun 20, 2018 at 10:25 AM Davor Bonaci  wrote:
>
>> 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.)
>>
>> But, it is something that warrants a discussion...
>>
>> On Wed, Jun 20, 2018 at 9:47 AM, Lukasz Cwik  wrote:
>>
>>> 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 look closely.

 Thanks.

 Davor

 [1] https://issues.apache.org/jira/browse/LEGAL-288

 On Wed, Jun 20, 2018 at 9:17 AM, Pablo Estrada 
 wrote:

> +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é <
>> j...@nanthrax.net> 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, Approve the release
>>> > [ ] -1, Do not approve the release (please provide specific
>>> comments)
>>> >
>>> > NB: this is the first release using Gradle, so don't be too harsh
>>> ;) A
>>> > PR about the release guide will follow thanks to this release.
>>> >
>>> > 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], which is signed with the key with fingerprint C8282E76 [3],
>>> > * all artifacts to be deployed to the Maven Central Repository [4],
>>> > * source code tag "v2.5.0-RC2" [5],
>>> > * website pull request listing the release and publishing the API
>>> > reference manual [6].
>>> > * Java artifacts were built with Gradle 4.7 (wrapper) and
>>> OpenJDK/Oracle
>>> > JDK 1.8.0_172 (Oracle Corporation 25.172-b11).
>>> > * Python artifacts are deployed along with the source release to
>>> the
>>> > dist.apache.org [2].
>>> >
>>> > The vote will be open for at least 72 hours. It is adopted by
>>> majority
>>> > approval, with at least 3 PMC affirmative votes.
>>> >
>>> > Thanks,
>>> > JB
>>> >
>>> > [1]
>>> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
>>> projectId=12319527&version=12342847
>>> > [2] https://dist.apache.org/repos/dist/dev/beam/2.5.0/
>>> > [3] https://dist.apache.org/repos/dist/release/beam/KEYS
>>> > [4] https://repository.apache.org/content/repositories/
>>> orgapachebeam-1043/
>>> > [5] https://github.com/apache/beam/tree/v2.5.0-RC2
>>> > [6] https://github.com/apache/beam-site/pull/463
>>> >
>>>
>>> --
>>> Jean-Baptiste Onofré
>>> jbono...@apache.org
>>> http://blog.nanthrax.net
>>> Talend - http://www.talend.com
>>>
>> --
> Got feedback? go/pabloem-feedback
> 
>


>>

Re: Broken links to releases

[Thomas Weise]

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 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 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 the better).
>>
>

Re: Broken links to releases

[Lukasz Cwik]

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 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 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 the better).
>>>
>>
>

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

[Pablo Estrada]

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:
https://github.com/pabloem/incubator-beam/archive/v2.5.0-TEST-ARCHIVE.zip
Best
-P.

On Wed, Jun 20, 2018 at 11:00 AM Ahmet Altay  wrote:

> 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 there is a resolution to the issue.
>
> Ahmet
>
> On Wed, Jun 20, 2018 at 10:46 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:
>>
>> beam-release-2.5.0/gradle.properties
>> beam-release-2.5.0/gradle/
>> beam-release-2.5.0/gradle/wrapper/
>> beam-release-2.5.0/gradle/wrapper/gradle-wrapper.jar
>> beam-release-2.5.0/gradle/wrapper/gradle-wrapper.properties
>> beam-release-2.5.0/gradlew
>> beam-release-2.5.0/gradlew.bat
>>
>> LEGAL-288 is unresolved, but looks like the mostly likely result is that
>> we must remove gradle-wrapper.jar. This matches ASF policy about putting
>> any binary artifact in the source zip. Apache Fineract is one place we
>> could look for an example of doing exactly this.
>>
>> In the past, we have manually tweaked the zip to remove extraneous files
>> without rolling a new RC & vote. Can do that here, since the release has
>> been thoroughly vetted?
>>
>> Kenn
>>
>> On Wed, Jun 20, 2018 at 10:25 AM Davor Bonaci  wrote:
>>
>>> 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.)
>>>
>>> But, it is something that warrants a discussion...
>>>
>>> On Wed, Jun 20, 2018 at 9:47 AM, Lukasz Cwik  wrote:
>>>
 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 look closely.
>
> Thanks.
>
> Davor
>
> [1] https://issues.apache.org/jira/browse/LEGAL-288
>
> On Wed, Jun 20, 2018 at 9:17 AM, Pablo Estrada 
> wrote:
>
>> +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é <
>>> j...@nanthrax.net> 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, Approve the release
 > [ ] -1, Do not approve the release (please provide specific
 comments)
 >
 > NB: this is the first release using Gradle, so don't be too harsh
 ;) A
 > PR about the release guide will follow thanks to this release.
 >
 > 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], which is signed with the key with fingerprint C8282E76 [3],
 > * all artifacts to be deployed to the Maven Central Repository
 [4],
 > * source code tag "v2.5.0-RC2" [5],
 > * website pull request listing the release and publishing the API
 > reference manual [6].
 > * Java artifacts were built with Gradle 4.7 (wrapper) and
 OpenJDK/Oracle
 > JDK 1.8.0_172 (Oracle Corporation 25.172-b11).
 > * Python artifacts are deployed along with the source release to
 the
 > dist.apache.org [2].
 >
 > The vote will be open for at least 72 hours. It is adopted by
 majority
 > approval, with at least 3 PMC affirmative votes.
 >
 > Thanks,
 > JB
 >
 > [1]
 >
 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527&version=12342847
 > [2] https://dist.apache.org/repos/dist/dev/beam/2.5.0/
 > [3] https://dist.apache.org/repos/dist/release/beam/KEYS
 > [4]
 https://repository.apache.org/content/repositories/or

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

[Ahmet Altay]

+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 Estrada  wrote:

> 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: https://github.com/pabloem/incubator-beam/
> archive/v2.5.0-TEST-ARCHIVE.zip
> Best
> -P.
>
> On Wed, Jun 20, 2018 at 11:00 AM Ahmet Altay  wrote:
>
>> 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 there is a resolution to the issue.
>>
>> Ahmet
>>
>> On Wed, Jun 20, 2018 at 10:46 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:
>>>
>>> beam-release-2.5.0/gradle.properties
>>> beam-release-2.5.0/gradle/
>>> beam-release-2.5.0/gradle/wrapper/
>>> beam-release-2.5.0/gradle/wrapper/gradle-wrapper.jar
>>> beam-release-2.5.0/gradle/wrapper/gradle-wrapper.properties
>>> beam-release-2.5.0/gradlew
>>> beam-release-2.5.0/gradlew.bat
>>>
>>> LEGAL-288 is unresolved, but looks like the mostly likely result is that
>>> we must remove gradle-wrapper.jar. This matches ASF policy about putting
>>> any binary artifact in the source zip. Apache Fineract is one place we
>>> could look for an example of doing exactly this.
>>>
>>> In the past, we have manually tweaked the zip to remove extraneous files
>>> without rolling a new RC & vote. Can do that here, since the release has
>>> been thoroughly vetted?
>>>
>>> Kenn
>>>
>>> On Wed, Jun 20, 2018 at 10:25 AM Davor Bonaci  wrote:
>>>
 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.)

 But, it is something that warrants a discussion...

 On Wed, Jun 20, 2018 at 9:47 AM, Lukasz Cwik  wrote:

> 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 look closely.
>>
>> Thanks.
>>
>> Davor
>>
>> [1] https://issues.apache.org/jira/browse/LEGAL-288
>>
>> On Wed, Jun 20, 2018 at 9:17 AM, Pablo Estrada 
>> wrote:
>>
>>> +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é <
 j...@nanthrax.net> 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, Approve the release
> > [ ] -1, Do not approve the release (please provide specific
> comments)
> >
> > NB: this is the first release using Gradle, so don't be too
> harsh ;) A
> > PR about the release guide will follow thanks to this release.
> >
> > 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], which is signed with the key with fingerprint C8282E76 [3],
> > * all artifacts to be deployed to the Maven Central Repository
> [4],
> > * source code tag "v2.5.0-RC2" [5],
> > * website pull request listing the release and publishing the API
> > reference manual [6].
> > * Java artifacts were built with Gradle 4.7 (wrapper) and
> OpenJDK/Oracle
> > JDK 1.8.0_172 (Oracle Corporation 25.172-b11).
> > * Python artifacts are deployed along with the source release to
> the
> > dist.apache.org [2].
> >
> > The vote will be open for at least 72 hours. It is adopted b

Re: Broken links to releases

[Kenneth Knowles]

+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
>> 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 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 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 the better).

>>>
>>