You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beam.apache.org by Jean-Baptiste Onofré <jb...@nanthrax.net> on 2018/06/17 05:18:08 UTC
[VOTE] Apache Beam, version 2.5.0, release candidate #2
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
Re: [VOTE] Apache Beam, version 2.5.0, release candidate #2
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi Pablo,
your vote is not binding: you are committer, not PMC member.
So, your vote is
+1 (non binding)
Regards
JB
On 20/06/2018 18:17, Pablo Estrada wrote:
> +1 (binding)
>
> On Wed, Jun 20, 2018 at 9:08 AM Lukasz Cwik <lcwik@google.com
> <ma...@google.com>> wrote:
>
> +1 (binding)
>
> On Tue, Jun 19, 2018 at 10:39 PM Jean-Baptiste Onofré
> <jb@nanthrax.net <ma...@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 <http://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 <http://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é
> jbonofre@apache.org <ma...@apache.org>
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
> --
> Got feedback? go/pabloem-feedback
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: [VOTE] Apache Beam, version 2.5.0, release candidate #2
Posted by Alexey Romanenko <ar...@gmail.com>.
+1, verified Spark with streaming (KafkaIO) and batch (ParquetIO).
WBR,
Alexey
> On 20 Jun 2018, at 22:53, Ahmet Altay <al...@google.com> wrote:
>
> +1, Thank you JB.
>
> JB, python wheel files are not included in https://dist.apache.org/repos/dist/dev/beam/2.5.0/ <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 <pabloem@google.com <ma...@google.com>> wrote:
> Since we use git-published archives to push to dist.apache.org <http://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 <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 <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 <altay@google.com <ma...@google.com>> 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 <klk@google.com <ma...@google.com>> 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 <davor@apache.org <ma...@apache.org>> 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 <lcwik@google.com <ma...@google.com>> wrote:
> Davor, please -1 the release if you believe LEGAL-288 applies.
>
> On Wed, Jun 20, 2018 at 9:37 AM Davor Bonaci <davor@apache.org <ma...@apache.org>> 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 <https://issues.apache.org/jira/browse/LEGAL-288>
>
> On Wed, Jun 20, 2018 at 9:17 AM, Pablo Estrada <pabloem@google.com <ma...@google.com>> wrote:
> +1 (binding)
>
> On Wed, Jun 20, 2018 at 9:08 AM Lukasz Cwik <lcwik@google.com <ma...@google.com>> wrote:
> +1 (binding)
>
> On Tue, Jun 19, 2018 at 10:39 PM Jean-Baptiste Onofré <jb@nanthrax.net <ma...@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 <http://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 <http://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 <https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527&version=12342847>
> > [2] https://dist.apache.org/repos/dist/dev/beam/2.5.0/ <https://dist.apache.org/repos/dist/dev/beam/2.5.0/>
> > [3] https://dist.apache.org/repos/dist/release/beam/KEYS <https://dist.apache.org/repos/dist/release/beam/KEYS>
> > [4] https://repository.apache.org/content/repositories/orgapachebeam-1043/ <https://repository.apache.org/content/repositories/orgapachebeam-1043/>
> > [5] https://github.com/apache/beam/tree/v2.5.0-RC2 <https://github.com/apache/beam/tree/v2.5.0-RC2>
> > [6] https://github.com/apache/beam-site/pull/463 <https://github.com/apache/beam-site/pull/463>
> >
>
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org <ma...@apache.org>
> http://blog.nanthrax.net <http://blog.nanthrax.net/>
> Talend - http://www.talend.com <http://www.talend.com/>
> --
> Got feedback? go/pabloem-feedback <https://goto.google.com/pabloem-feedback>
>
>
> --
> Got feedback? go/pabloem-feedback <https://goto.google.com/pabloem-feedback>
Re: [VOTE] Apache Beam, version 2.5.0, release candidate #2
Posted by Ahmet Altay <al...@google.com>.
+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 <pa...@google.com> 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 <al...@google.com> 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 <kl...@google.com> 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 <da...@apache.org> 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 <lc...@google.com> wrote:
>>>>
>>>>> Davor, please -1 the release if you believe LEGAL-288 applies.
>>>>>
>>>>> On Wed, Jun 20, 2018 at 9:37 AM Davor Bonaci <da...@apache.org> 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 <pa...@google.com>
>>>>>> wrote:
>>>>>>
>>>>>>> +1 (binding)
>>>>>>>
>>>>>>> On Wed, Jun 20, 2018 at 9:08 AM Lukasz Cwik <lc...@google.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> +1 (binding)
>>>>>>>>
>>>>>>>> On Tue, Jun 19, 2018 at 10:39 PM Jean-Baptiste Onofré <
>>>>>>>> jb@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é
>>>>>>>>> jbonofre@apache.org
>>>>>>>>> http://blog.nanthrax.net
>>>>>>>>> Talend - http://www.talend.com
>>>>>>>>>
>>>>>>>> --
>>>>>>> Got feedback? go/pabloem-feedback
>>>>>>> <https://goto.google.com/pabloem-feedback>
>>>>>>>
>>>>>>
>>>>>>
>>>>
>> --
> Got feedback? go/pabloem-feedback
> <https://goto.google.com/pabloem-feedback>
>
Re: [VOTE] Apache Beam, version 2.5.0, release candidate #2
Posted by Pablo Estrada <pa...@google.com>.
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 <al...@google.com> 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 <kl...@google.com> 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 <da...@apache.org> 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 <lc...@google.com> wrote:
>>>
>>>> Davor, please -1 the release if you believe LEGAL-288 applies.
>>>>
>>>> On Wed, Jun 20, 2018 at 9:37 AM Davor Bonaci <da...@apache.org> 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 <pa...@google.com>
>>>>> wrote:
>>>>>
>>>>>> +1 (binding)
>>>>>>
>>>>>> On Wed, Jun 20, 2018 at 9:08 AM Lukasz Cwik <lc...@google.com> wrote:
>>>>>>
>>>>>>> +1 (binding)
>>>>>>>
>>>>>>> On Tue, Jun 19, 2018 at 10:39 PM Jean-Baptiste Onofré <
>>>>>>> jb@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é
>>>>>>>> jbonofre@apache.org
>>>>>>>> http://blog.nanthrax.net
>>>>>>>> Talend - http://www.talend.com
>>>>>>>>
>>>>>>> --
>>>>>> Got feedback? go/pabloem-feedback
>>>>>> <https://goto.google.com/pabloem-feedback>
>>>>>>
>>>>>
>>>>>
>>>
> --
Got feedback? go/pabloem-feedback
Re: [VOTE] Apache Beam, version 2.5.0, release candidate #2
Posted by Ahmet Altay <al...@google.com>.
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 <kl...@google.com> 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 <da...@apache.org> 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 <lc...@google.com> wrote:
>>
>>> Davor, please -1 the release if you believe LEGAL-288 applies.
>>>
>>> On Wed, Jun 20, 2018 at 9:37 AM Davor Bonaci <da...@apache.org> 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 <pa...@google.com>
>>>> wrote:
>>>>
>>>>> +1 (binding)
>>>>>
>>>>> On Wed, Jun 20, 2018 at 9:08 AM Lukasz Cwik <lc...@google.com> wrote:
>>>>>
>>>>>> +1 (binding)
>>>>>>
>>>>>> On Tue, Jun 19, 2018 at 10:39 PM Jean-Baptiste Onofré <
>>>>>> jb@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é
>>>>>>> jbonofre@apache.org
>>>>>>> http://blog.nanthrax.net
>>>>>>> Talend - http://www.talend.com
>>>>>>>
>>>>>> --
>>>>> Got feedback? go/pabloem-feedback
>>>>> <https://goto.google.com/pabloem-feedback>
>>>>>
>>>>
>>>>
>>
Re: [VOTE] Apache Beam, version 2.5.0, release candidate #2
Posted by Lukasz Cwik <lc...@google.com>.
SGTM, if its just dropping gradle-wrapper.jar file from the source zip.
On Wed, Jun 20, 2018 at 10:47 AM Kenneth Knowles <kl...@google.com> 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 <da...@apache.org> 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 <lc...@google.com> wrote:
>>
>>> Davor, please -1 the release if you believe LEGAL-288 applies.
>>>
>>> On Wed, Jun 20, 2018 at 9:37 AM Davor Bonaci <da...@apache.org> 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 <pa...@google.com>
>>>> wrote:
>>>>
>>>>> +1 (binding)
>>>>>
>>>>> On Wed, Jun 20, 2018 at 9:08 AM Lukasz Cwik <lc...@google.com> wrote:
>>>>>
>>>>>> +1 (binding)
>>>>>>
>>>>>> On Tue, Jun 19, 2018 at 10:39 PM Jean-Baptiste Onofré <
>>>>>> jb@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é
>>>>>>> jbonofre@apache.org
>>>>>>> http://blog.nanthrax.net
>>>>>>> Talend - http://www.talend.com
>>>>>>>
>>>>>> --
>>>>> Got feedback? go/pabloem-feedback
>>>>> <https://goto.google.com/pabloem-feedback>
>>>>>
>>>>
>>>>
>>
Re: [VOTE] Apache Beam, version 2.5.0, release candidate #2
Posted by Kenneth Knowles <kl...@google.com>.
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 <da...@apache.org> 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 <lc...@google.com> wrote:
>
>> Davor, please -1 the release if you believe LEGAL-288 applies.
>>
>> On Wed, Jun 20, 2018 at 9:37 AM Davor Bonaci <da...@apache.org> 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 <pa...@google.com>
>>> wrote:
>>>
>>>> +1 (binding)
>>>>
>>>> On Wed, Jun 20, 2018 at 9:08 AM Lukasz Cwik <lc...@google.com> wrote:
>>>>
>>>>> +1 (binding)
>>>>>
>>>>> On Tue, Jun 19, 2018 at 10:39 PM Jean-Baptiste Onofré <jb...@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é
>>>>>> jbonofre@apache.org
>>>>>> http://blog.nanthrax.net
>>>>>> Talend - http://www.talend.com
>>>>>>
>>>>> --
>>>> Got feedback? go/pabloem-feedback
>>>> <https://goto.google.com/pabloem-feedback>
>>>>
>>>
>>>
>
Re: [VOTE] Apache Beam, version 2.5.0, release candidate #2
Posted by Davor Bonaci <da...@apache.org>.
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 <lc...@google.com> wrote:
> Davor, please -1 the release if you believe LEGAL-288 applies.
>
> On Wed, Jun 20, 2018 at 9:37 AM Davor Bonaci <da...@apache.org> 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 <pa...@google.com>
>> wrote:
>>
>>> +1 (binding)
>>>
>>> On Wed, Jun 20, 2018 at 9:08 AM Lukasz Cwik <lc...@google.com> wrote:
>>>
>>>> +1 (binding)
>>>>
>>>> On Tue, Jun 19, 2018 at 10:39 PM Jean-Baptiste Onofré <jb...@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?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é
>>>>> jbonofre@apache.org
>>>>> http://blog.nanthrax.net
>>>>> Talend - http://www.talend.com
>>>>>
>>>> --
>>> Got feedback? go/pabloem-feedback
>>> <https://goto.google.com/pabloem-feedback>
>>>
>>
>>
Re: [VOTE] Apache Beam, version 2.5.0, release candidate #2
Posted by Lukasz Cwik <lc...@google.com>.
Davor, please -1 the release if you believe LEGAL-288 applies.
On Wed, Jun 20, 2018 at 9:37 AM Davor Bonaci <da...@apache.org> 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 <pa...@google.com> wrote:
>
>> +1 (binding)
>>
>> On Wed, Jun 20, 2018 at 9:08 AM Lukasz Cwik <lc...@google.com> wrote:
>>
>>> +1 (binding)
>>>
>>> On Tue, Jun 19, 2018 at 10:39 PM Jean-Baptiste Onofré <jb...@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é
>>>> jbonofre@apache.org
>>>> http://blog.nanthrax.net
>>>> Talend - http://www.talend.com
>>>>
>>> --
>> Got feedback? go/pabloem-feedback
>> <https://goto.google.com/pabloem-feedback>
>>
>
>
Re: [VOTE] Apache Beam, version 2.5.0, release candidate #2
Posted by Davor Bonaci <da...@apache.org>.
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 <pa...@google.com> wrote:
> +1 (binding)
>
> On Wed, Jun 20, 2018 at 9:08 AM Lukasz Cwik <lc...@google.com> wrote:
>
>> +1 (binding)
>>
>> On Tue, Jun 19, 2018 at 10:39 PM Jean-Baptiste Onofré <jb...@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é
>>> jbonofre@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
Posted by Pablo Estrada <pa...@google.com>.
+1 (binding)
On Wed, Jun 20, 2018 at 9:08 AM Lukasz Cwik <lc...@google.com> wrote:
> +1 (binding)
>
> On Tue, Jun 19, 2018 at 10:39 PM Jean-Baptiste Onofré <jb...@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é
>> jbonofre@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
Posted by Lukasz Cwik <lc...@google.com>.
+1 (binding)
On Tue, Jun 19, 2018 at 10:39 PM Jean-Baptiste Onofré <jb...@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é
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
Re: [VOTE] Apache Beam, version 2.5.0, release candidate #2
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
+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é
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: [VOTE] Apache Beam, version 2.5.0, release candidate #2
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Done,
by the way, I add to launch a gitbox resync for both beam and beam-site
repos.
Regards
JB
On 17/06/2018 19:32, Pablo Estrada wrote:
> Going to https://github.com/apache/beam/tree/v2.5.0-RC2 gives me a 404
> error. May need to push the label?
> Best
> -P.
>
> On Sun, Jun 17, 2018 at 1:15 AM Romain Manni-Bucau
> <rmannibucau@gmail.com <ma...@gmail.com>> wrote:
>
> +1 (same tests than for take #1)
>
> Le dim. 17 juin 2018 07:18, Jean-Baptiste Onofré <jb@nanthrax.net
> <ma...@nanthrax.net>> a écrit :
>
> 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 <http://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 <http://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
>
> --
> Got feedback? go/pabloem-feedback
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: [VOTE] Apache Beam, version 2.5.0, release candidate #2
Posted by Yifan Zou <yi...@google.com>.
follow up the previous email. The automated validation test verified the
wheel below:
apache_beam-2.5.0-cp27-cp27mu-manylinux1_x86_64.whl
On Tue, Jun 19, 2018 at 5:11 PM Yifan Zou <yi...@google.com> wrote:
> +1
> Verified Python wheels. They are good.
> https://builds.apache.org/job/beam_PostRelease_Python_Candidate/117/
>
>
> On Tue, Jun 19, 2018 at 10:32 AM Udi Meiri <eh...@google.com> wrote:
>
>> +1
>>
>> On Mon, Jun 18, 2018 at 6:16 PM Boyuan Zhang <bo...@google.com> wrote:
>>
>>> Follow up with pervious email( sorry for the inconvenience).
>>>
>>> Hey JB,
>>>
>>> If you haven't built python wheels yet, then you can use files in the
>>> previous email to move forward. If you have done all of them, then please
>>> ignore previous email.
>>>
>>> Thanks so much for your help.
>>>
>>> Boyuan
>>>
>>> On Mon, Jun 18, 2018 at 6:08 PM Boyuan Zhang <bo...@google.com> wrote:
>>>
>>>> Hey JB,
>>>>
>>>> I built python wheels and you can get them here:
>>>> https://storage.googleapis.com/python_wheels/python_wheels.zip. You
>>>> probably need to sign them and upload them into
>>>> https://dist.apache.org/repos/dist/dev/beam/2.5.0/ like what we did
>>>> for 2.4.0: https://dist.apache.org/repos/dist/dev/beam/2.4.0/ . After
>>>> you upload, we can do more validations on python wheels.
>>>>
>>>> Boyuan
>>>>
>>>> On Mon, Jun 18, 2018 at 4:49 PM Pablo Estrada <pa...@google.com>
>>>> wrote:
>>>>
>>>>> +0.9
>>>>>
>>>>> I've run the Mobile Gaming examples in Java+Dataflow, and others have
>>>>> documented their tests in the spreadsheet[1]. All seems to work well.
>>>>> We will need the wheel files to be available, and run a few
>>>>> validations on them, but other than that, the release looks good to me.
>>>>>
>>>>> Best
>>>>> -P.
>>>>>
>>>>> [1]
>>>>> https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=152451807
>>>>>
>>>>> On Mon, Jun 18, 2018 at 10:08 AM Jean-Baptiste Onofré <jb...@nanthrax.net>
>>>>> wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I thought I did it, let me double check.
>>>>>>
>>>>>> Regards
>>>>>> JB
>>>>>>
>>>>>> On 18/06/2018 19:01, Boyuan Zhang wrote:
>>>>>> > Hey JB,
>>>>>> >
>>>>>> > Could you please also build python wheels for RC2 and stage them in
>>>>>> > https://dist.apache.org/repos/dist/dev/beam/2.5.0/? There are some
>>>>>> > instructions in this PR:
>>>>>> https://github.com/apache/beam-site/pull/467.
>>>>>> > Hope it can be helpful.
>>>>>> >
>>>>>> > Thanks.
>>>>>> > Boyuan
>>>>>> >
>>>>>> > On Sun, Jun 17, 2018 at 9:22 PM Jean-Baptiste Onofré <
>>>>>> jb@nanthrax.net
>>>>>> > <ma...@nanthrax.net>> wrote:
>>>>>> >
>>>>>> > s/add/had/g
>>>>>> >
>>>>>> > On 17/06/2018 19:32, Pablo Estrada wrote:
>>>>>> > > Going to https://github.com/apache/beam/tree/v2.5.0-RC2 gives
>>>>>> me a 404
>>>>>> > > error. May need to push the label?
>>>>>> > > Best
>>>>>> > > -P.
>>>>>> > >
>>>>>> > > On Sun, Jun 17, 2018 at 1:15 AM Romain Manni-Bucau
>>>>>> > > <rmannibucau@gmail.com <ma...@gmail.com>
>>>>>> > <mailto:rmannibucau@gmail.com <ma...@gmail.com>>>
>>>>>> wrote:
>>>>>> > >
>>>>>> > > +1 (same tests than for take #1)
>>>>>> > >
>>>>>> > > Le dim. 17 juin 2018 07:18, Jean-Baptiste Onofré
>>>>>> > <jb@nanthrax.net <ma...@nanthrax.net>
>>>>>> > > <mailto:jb@nanthrax.net <ma...@nanthrax.net>>> a
>>>>>> écrit :
>>>>>> > >
>>>>>> > > 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 <http://dist.apache.org>
>>>>>> > <http://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 <http://dist.apache.org>
>>>>>> > <http://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
>>>>>> > >
>>>>>> > > --
>>>>>> > > Got feedback? go/pabloem-feedback
>>>>>> <https://goto.google.com/pabloem-feedback>
>>>>>> > <https://goto.google.com/pabloem-feedback>
>>>>>> >
>>>>>> > --
>>>>>> > Jean-Baptiste Onofré
>>>>>> > jbonofre@apache.org <ma...@apache.org>
>>>>>> > http://blog.nanthrax.net
>>>>>> > Talend - http://www.talend.com
>>>>>> >
>>>>>>
>>>>> --
>>>>> Got feedback? go/pabloem-feedback
>>>>> <https://goto.google.com/pabloem-feedback>
>>>>>
>>>>
Re: [VOTE] Apache Beam, version 2.5.0, release candidate #2
Posted by Yifan Zou <yi...@google.com>.
+1
Verified Python wheels. They are good.
https://builds.apache.org/job/beam_PostRelease_Python_Candidate/117/
On Tue, Jun 19, 2018 at 10:32 AM Udi Meiri <eh...@google.com> wrote:
> +1
>
> On Mon, Jun 18, 2018 at 6:16 PM Boyuan Zhang <bo...@google.com> wrote:
>
>> Follow up with pervious email( sorry for the inconvenience).
>>
>> Hey JB,
>>
>> If you haven't built python wheels yet, then you can use files in the
>> previous email to move forward. If you have done all of them, then please
>> ignore previous email.
>>
>> Thanks so much for your help.
>>
>> Boyuan
>>
>> On Mon, Jun 18, 2018 at 6:08 PM Boyuan Zhang <bo...@google.com> wrote:
>>
>>> Hey JB,
>>>
>>> I built python wheels and you can get them here:
>>> https://storage.googleapis.com/python_wheels/python_wheels.zip. You
>>> probably need to sign them and upload them into
>>> https://dist.apache.org/repos/dist/dev/beam/2.5.0/ like what we did for
>>> 2.4.0: https://dist.apache.org/repos/dist/dev/beam/2.4.0/ . After you
>>> upload, we can do more validations on python wheels.
>>>
>>> Boyuan
>>>
>>> On Mon, Jun 18, 2018 at 4:49 PM Pablo Estrada <pa...@google.com>
>>> wrote:
>>>
>>>> +0.9
>>>>
>>>> I've run the Mobile Gaming examples in Java+Dataflow, and others have
>>>> documented their tests in the spreadsheet[1]. All seems to work well.
>>>> We will need the wheel files to be available, and run a few validations
>>>> on them, but other than that, the release looks good to me.
>>>>
>>>> Best
>>>> -P.
>>>>
>>>> [1]
>>>> https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=152451807
>>>>
>>>> On Mon, Jun 18, 2018 at 10:08 AM Jean-Baptiste Onofré <jb...@nanthrax.net>
>>>> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I thought I did it, let me double check.
>>>>>
>>>>> Regards
>>>>> JB
>>>>>
>>>>> On 18/06/2018 19:01, Boyuan Zhang wrote:
>>>>> > Hey JB,
>>>>> >
>>>>> > Could you please also build python wheels for RC2 and stage them in
>>>>> > https://dist.apache.org/repos/dist/dev/beam/2.5.0/? There are some
>>>>> > instructions in this PR:
>>>>> https://github.com/apache/beam-site/pull/467.
>>>>> > Hope it can be helpful.
>>>>> >
>>>>> > Thanks.
>>>>> > Boyuan
>>>>> >
>>>>> > On Sun, Jun 17, 2018 at 9:22 PM Jean-Baptiste Onofré <
>>>>> jb@nanthrax.net
>>>>> > <ma...@nanthrax.net>> wrote:
>>>>> >
>>>>> > s/add/had/g
>>>>> >
>>>>> > On 17/06/2018 19:32, Pablo Estrada wrote:
>>>>> > > Going to https://github.com/apache/beam/tree/v2.5.0-RC2 gives
>>>>> me a 404
>>>>> > > error. May need to push the label?
>>>>> > > Best
>>>>> > > -P.
>>>>> > >
>>>>> > > On Sun, Jun 17, 2018 at 1:15 AM Romain Manni-Bucau
>>>>> > > <rmannibucau@gmail.com <ma...@gmail.com>
>>>>> > <mailto:rmannibucau@gmail.com <ma...@gmail.com>>>
>>>>> wrote:
>>>>> > >
>>>>> > > +1 (same tests than for take #1)
>>>>> > >
>>>>> > > Le dim. 17 juin 2018 07:18, Jean-Baptiste Onofré
>>>>> > <jb@nanthrax.net <ma...@nanthrax.net>
>>>>> > > <mailto:jb@nanthrax.net <ma...@nanthrax.net>>> a
>>>>> écrit :
>>>>> > >
>>>>> > > 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 <http://dist.apache.org>
>>>>> > <http://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 <http://dist.apache.org>
>>>>> > <http://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
>>>>> > >
>>>>> > > --
>>>>> > > Got feedback? go/pabloem-feedback
>>>>> <https://goto.google.com/pabloem-feedback>
>>>>> > <https://goto.google.com/pabloem-feedback>
>>>>> >
>>>>> > --
>>>>> > Jean-Baptiste Onofré
>>>>> > jbonofre@apache.org <ma...@apache.org>
>>>>> > http://blog.nanthrax.net
>>>>> > Talend - http://www.talend.com
>>>>> >
>>>>>
>>>> --
>>>> Got feedback? go/pabloem-feedback
>>>> <https://goto.google.com/pabloem-feedback>
>>>>
>>>
Re: [VOTE] Apache Beam, version 2.5.0, release candidate #2
Posted by Udi Meiri <eh...@google.com>.
+1
On Mon, Jun 18, 2018 at 6:16 PM Boyuan Zhang <bo...@google.com> wrote:
> Follow up with pervious email( sorry for the inconvenience).
>
> Hey JB,
>
> If you haven't built python wheels yet, then you can use files in the
> previous email to move forward. If you have done all of them, then please
> ignore previous email.
>
> Thanks so much for your help.
>
> Boyuan
>
> On Mon, Jun 18, 2018 at 6:08 PM Boyuan Zhang <bo...@google.com> wrote:
>
>> Hey JB,
>>
>> I built python wheels and you can get them here:
>> https://storage.googleapis.com/python_wheels/python_wheels.zip. You
>> probably need to sign them and upload them into
>> https://dist.apache.org/repos/dist/dev/beam/2.5.0/ like what we did for
>> 2.4.0: https://dist.apache.org/repos/dist/dev/beam/2.4.0/ . After you
>> upload, we can do more validations on python wheels.
>>
>> Boyuan
>>
>> On Mon, Jun 18, 2018 at 4:49 PM Pablo Estrada <pa...@google.com> wrote:
>>
>>> +0.9
>>>
>>> I've run the Mobile Gaming examples in Java+Dataflow, and others have
>>> documented their tests in the spreadsheet[1]. All seems to work well.
>>> We will need the wheel files to be available, and run a few validations
>>> on them, but other than that, the release looks good to me.
>>>
>>> Best
>>> -P.
>>>
>>> [1]
>>> https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=152451807
>>>
>>> On Mon, Jun 18, 2018 at 10:08 AM Jean-Baptiste Onofré <jb...@nanthrax.net>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> I thought I did it, let me double check.
>>>>
>>>> Regards
>>>> JB
>>>>
>>>> On 18/06/2018 19:01, Boyuan Zhang wrote:
>>>> > Hey JB,
>>>> >
>>>> > Could you please also build python wheels for RC2 and stage them in
>>>> > https://dist.apache.org/repos/dist/dev/beam/2.5.0/? There are some
>>>> > instructions in this PR: https://github.com/apache/beam-site/pull/467
>>>> .
>>>> > Hope it can be helpful.
>>>> >
>>>> > Thanks.
>>>> > Boyuan
>>>> >
>>>> > On Sun, Jun 17, 2018 at 9:22 PM Jean-Baptiste Onofré <jb@nanthrax.net
>>>> > <ma...@nanthrax.net>> wrote:
>>>> >
>>>> > s/add/had/g
>>>> >
>>>> > On 17/06/2018 19:32, Pablo Estrada wrote:
>>>> > > Going to https://github.com/apache/beam/tree/v2.5.0-RC2 gives
>>>> me a 404
>>>> > > error. May need to push the label?
>>>> > > Best
>>>> > > -P.
>>>> > >
>>>> > > On Sun, Jun 17, 2018 at 1:15 AM Romain Manni-Bucau
>>>> > > <rmannibucau@gmail.com <ma...@gmail.com>
>>>> > <mailto:rmannibucau@gmail.com <ma...@gmail.com>>>
>>>> wrote:
>>>> > >
>>>> > > +1 (same tests than for take #1)
>>>> > >
>>>> > > Le dim. 17 juin 2018 07:18, Jean-Baptiste Onofré
>>>> > <jb@nanthrax.net <ma...@nanthrax.net>
>>>> > > <mailto:jb@nanthrax.net <ma...@nanthrax.net>>> a
>>>> écrit :
>>>> > >
>>>> > > 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 <http://dist.apache.org>
>>>> > <http://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 <http://dist.apache.org>
>>>> > <http://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
>>>> > >
>>>> > > --
>>>> > > Got feedback? go/pabloem-feedback
>>>> <https://goto.google.com/pabloem-feedback>
>>>> > <https://goto.google.com/pabloem-feedback>
>>>> >
>>>> > --
>>>> > Jean-Baptiste Onofré
>>>> > jbonofre@apache.org <ma...@apache.org>
>>>> > http://blog.nanthrax.net
>>>> > Talend - http://www.talend.com
>>>> >
>>>>
>>> --
>>> Got feedback? go/pabloem-feedback
>>> <https://goto.google.com/pabloem-feedback>
>>>
>>
Re: [VOTE] Apache Beam, version 2.5.0, release candidate #2
Posted by Boyuan Zhang <bo...@google.com>.
Follow up with pervious email( sorry for the inconvenience).
Hey JB,
If you haven't built python wheels yet, then you can use files in the
previous email to move forward. If you have done all of them, then please
ignore previous email.
Thanks so much for your help.
Boyuan
On Mon, Jun 18, 2018 at 6:08 PM Boyuan Zhang <bo...@google.com> wrote:
> Hey JB,
>
> I built python wheels and you can get them here:
> https://storage.googleapis.com/python_wheels/python_wheels.zip. You
> probably need to sign them and upload them into
> https://dist.apache.org/repos/dist/dev/beam/2.5.0/ like what we did for
> 2.4.0: https://dist.apache.org/repos/dist/dev/beam/2.4.0/ . After you
> upload, we can do more validations on python wheels.
>
> Boyuan
>
> On Mon, Jun 18, 2018 at 4:49 PM Pablo Estrada <pa...@google.com> wrote:
>
>> +0.9
>>
>> I've run the Mobile Gaming examples in Java+Dataflow, and others have
>> documented their tests in the spreadsheet[1]. All seems to work well.
>> We will need the wheel files to be available, and run a few validations
>> on them, but other than that, the release looks good to me.
>>
>> Best
>> -P.
>>
>> [1]
>> https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=152451807
>>
>> On Mon, Jun 18, 2018 at 10:08 AM Jean-Baptiste Onofré <jb...@nanthrax.net>
>> wrote:
>>
>>> Hi,
>>>
>>> I thought I did it, let me double check.
>>>
>>> Regards
>>> JB
>>>
>>> On 18/06/2018 19:01, Boyuan Zhang wrote:
>>> > Hey JB,
>>> >
>>> > Could you please also build python wheels for RC2 and stage them in
>>> > https://dist.apache.org/repos/dist/dev/beam/2.5.0/? There are some
>>> > instructions in this PR: https://github.com/apache/beam-site/pull/467
>>> .
>>> > Hope it can be helpful.
>>> >
>>> > Thanks.
>>> > Boyuan
>>> >
>>> > On Sun, Jun 17, 2018 at 9:22 PM Jean-Baptiste Onofré <jb@nanthrax.net
>>> > <ma...@nanthrax.net>> wrote:
>>> >
>>> > s/add/had/g
>>> >
>>> > On 17/06/2018 19:32, Pablo Estrada wrote:
>>> > > Going to https://github.com/apache/beam/tree/v2.5.0-RC2 gives
>>> me a 404
>>> > > error. May need to push the label?
>>> > > Best
>>> > > -P.
>>> > >
>>> > > On Sun, Jun 17, 2018 at 1:15 AM Romain Manni-Bucau
>>> > > <rmannibucau@gmail.com <ma...@gmail.com>
>>> > <mailto:rmannibucau@gmail.com <ma...@gmail.com>>>
>>> wrote:
>>> > >
>>> > > +1 (same tests than for take #1)
>>> > >
>>> > > Le dim. 17 juin 2018 07:18, Jean-Baptiste Onofré
>>> > <jb@nanthrax.net <ma...@nanthrax.net>
>>> > > <mailto:jb@nanthrax.net <ma...@nanthrax.net>>> a écrit :
>>> > >
>>> > > 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 <http://dist.apache.org>
>>> > <http://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 <http://dist.apache.org>
>>> > <http://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
>>> > >
>>> > > --
>>> > > Got feedback? go/pabloem-feedback
>>> <https://goto.google.com/pabloem-feedback>
>>> > <https://goto.google.com/pabloem-feedback>
>>> >
>>> > --
>>> > Jean-Baptiste Onofré
>>> > jbonofre@apache.org <ma...@apache.org>
>>> > http://blog.nanthrax.net
>>> > Talend - http://www.talend.com
>>> >
>>>
>> --
>> Got feedback? go/pabloem-feedback
>> <https://goto.google.com/pabloem-feedback>
>>
>
Re: [VOTE] Apache Beam, version 2.5.0, release candidate #2
Posted by Boyuan Zhang <bo...@google.com>.
Hey JB,
I built python wheels and you can get them here:
https://storage.googleapis.com/python_wheels/python_wheels.zip. You
probably need to sign them and upload them into
https://dist.apache.org/repos/dist/dev/beam/2.5.0/ like what we did for
2.4.0: https://dist.apache.org/repos/dist/dev/beam/2.4.0/ . After you
upload, we can do more validations on python wheels.
Boyuan
On Mon, Jun 18, 2018 at 4:49 PM Pablo Estrada <pa...@google.com> wrote:
> +0.9
>
> I've run the Mobile Gaming examples in Java+Dataflow, and others have
> documented their tests in the spreadsheet[1]. All seems to work well.
> We will need the wheel files to be available, and run a few validations on
> them, but other than that, the release looks good to me.
>
> Best
> -P.
>
> [1]
> https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=152451807
>
> On Mon, Jun 18, 2018 at 10:08 AM Jean-Baptiste Onofré <jb...@nanthrax.net>
> wrote:
>
>> Hi,
>>
>> I thought I did it, let me double check.
>>
>> Regards
>> JB
>>
>> On 18/06/2018 19:01, Boyuan Zhang wrote:
>> > Hey JB,
>> >
>> > Could you please also build python wheels for RC2 and stage them in
>> > https://dist.apache.org/repos/dist/dev/beam/2.5.0/? There are some
>> > instructions in this PR: https://github.com/apache/beam-site/pull/467.
>> > Hope it can be helpful.
>> >
>> > Thanks.
>> > Boyuan
>> >
>> > On Sun, Jun 17, 2018 at 9:22 PM Jean-Baptiste Onofré <jb@nanthrax.net
>> > <ma...@nanthrax.net>> wrote:
>> >
>> > s/add/had/g
>> >
>> > On 17/06/2018 19:32, Pablo Estrada wrote:
>> > > Going to https://github.com/apache/beam/tree/v2.5.0-RC2 gives me
>> a 404
>> > > error. May need to push the label?
>> > > Best
>> > > -P.
>> > >
>> > > On Sun, Jun 17, 2018 at 1:15 AM Romain Manni-Bucau
>> > > <rmannibucau@gmail.com <ma...@gmail.com>
>> > <mailto:rmannibucau@gmail.com <ma...@gmail.com>>>
>> wrote:
>> > >
>> > > +1 (same tests than for take #1)
>> > >
>> > > Le dim. 17 juin 2018 07:18, Jean-Baptiste Onofré
>> > <jb@nanthrax.net <ma...@nanthrax.net>
>> > > <mailto:jb@nanthrax.net <ma...@nanthrax.net>>> a écrit :
>> > >
>> > > 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 <http://dist.apache.org>
>> > <http://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 <http://dist.apache.org>
>> > <http://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
>> > >
>> > > --
>> > > Got feedback? go/pabloem-feedback
>> <https://goto.google.com/pabloem-feedback>
>> > <https://goto.google.com/pabloem-feedback>
>> >
>> > --
>> > Jean-Baptiste Onofré
>> > jbonofre@apache.org <ma...@apache.org>
>> > http://blog.nanthrax.net
>> > Talend - http://www.talend.com
>> >
>>
> --
> Got feedback? go/pabloem-feedback
> <https://goto.google.com/pabloem-feedback>
>
Re: [VOTE] Apache Beam, version 2.5.0, release candidate #2
Posted by Pablo Estrada <pa...@google.com>.
+0.9
I've run the Mobile Gaming examples in Java+Dataflow, and others have
documented their tests in the spreadsheet[1]. All seems to work well.
We will need the wheel files to be available, and run a few validations on
them, but other than that, the release looks good to me.
Best
-P.
[1]
https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=152451807
On Mon, Jun 18, 2018 at 10:08 AM Jean-Baptiste Onofré <jb...@nanthrax.net>
wrote:
> Hi,
>
> I thought I did it, let me double check.
>
> Regards
> JB
>
> On 18/06/2018 19:01, Boyuan Zhang wrote:
> > Hey JB,
> >
> > Could you please also build python wheels for RC2 and stage them in
> > https://dist.apache.org/repos/dist/dev/beam/2.5.0/? There are some
> > instructions in this PR: https://github.com/apache/beam-site/pull/467.
> > Hope it can be helpful.
> >
> > Thanks.
> > Boyuan
> >
> > On Sun, Jun 17, 2018 at 9:22 PM Jean-Baptiste Onofré <jb@nanthrax.net
> > <ma...@nanthrax.net>> wrote:
> >
> > s/add/had/g
> >
> > On 17/06/2018 19:32, Pablo Estrada wrote:
> > > Going to https://github.com/apache/beam/tree/v2.5.0-RC2 gives me
> a 404
> > > error. May need to push the label?
> > > Best
> > > -P.
> > >
> > > On Sun, Jun 17, 2018 at 1:15 AM Romain Manni-Bucau
> > > <rmannibucau@gmail.com <ma...@gmail.com>
> > <mailto:rmannibucau@gmail.com <ma...@gmail.com>>>
> wrote:
> > >
> > > +1 (same tests than for take #1)
> > >
> > > Le dim. 17 juin 2018 07:18, Jean-Baptiste Onofré
> > <jb@nanthrax.net <ma...@nanthrax.net>
> > > <mailto:jb@nanthrax.net <ma...@nanthrax.net>>> a écrit :
> > >
> > > 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 <http://dist.apache.org>
> > <http://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 <http://dist.apache.org>
> > <http://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
> > >
> > > --
> > > Got feedback? go/pabloem-feedback
> <https://goto.google.com/pabloem-feedback>
> > <https://goto.google.com/pabloem-feedback>
> >
> > --
> > Jean-Baptiste Onofré
> > jbonofre@apache.org <ma...@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
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi,
I thought I did it, let me double check.
Regards
JB
On 18/06/2018 19:01, Boyuan Zhang wrote:
> Hey JB,
>
> Could you please also build python wheels for RC2 and stage them in
> https://dist.apache.org/repos/dist/dev/beam/2.5.0/? There are some
> instructions in this PR: https://github.com/apache/beam-site/pull/467.
> Hope it can be helpful.
>
> Thanks.
> Boyuan
>
> On Sun, Jun 17, 2018 at 9:22 PM Jean-Baptiste Onofré <jb@nanthrax.net
> <ma...@nanthrax.net>> wrote:
>
> s/add/had/g
>
> On 17/06/2018 19:32, Pablo Estrada wrote:
> > Going to https://github.com/apache/beam/tree/v2.5.0-RC2 gives me a 404
> > error. May need to push the label?
> > Best
> > -P.
> >
> > On Sun, Jun 17, 2018 at 1:15 AM Romain Manni-Bucau
> > <rmannibucau@gmail.com <ma...@gmail.com>
> <mailto:rmannibucau@gmail.com <ma...@gmail.com>>> wrote:
> >
> > +1 (same tests than for take #1)
> >
> > Le dim. 17 juin 2018 07:18, Jean-Baptiste Onofré
> <jb@nanthrax.net <ma...@nanthrax.net>
> > <mailto:jb@nanthrax.net <ma...@nanthrax.net>>> a écrit :
> >
> > 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 <http://dist.apache.org>
> <http://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 <http://dist.apache.org>
> <http://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
> >
> > --
> > Got feedback? go/pabloem-feedback
> <https://goto.google.com/pabloem-feedback>
>
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org <ma...@apache.org>
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
Re: [VOTE] Apache Beam, version 2.5.0, release candidate #2
Posted by Boyuan Zhang <bo...@google.com>.
Hey JB,
Could you please also build python wheels for RC2 and stage them in
https://dist.apache.org/repos/dist/dev/beam/2.5.0/? There are some
instructions in this PR: https://github.com/apache/beam-site/pull/467.
Hope it can be helpful.
Thanks.
Boyuan
On Sun, Jun 17, 2018 at 9:22 PM Jean-Baptiste Onofré <jb...@nanthrax.net>
wrote:
> s/add/had/g
>
> On 17/06/2018 19:32, Pablo Estrada wrote:
> > Going to https://github.com/apache/beam/tree/v2.5.0-RC2 gives me a 404
> > error. May need to push the label?
> > Best
> > -P.
> >
> > On Sun, Jun 17, 2018 at 1:15 AM Romain Manni-Bucau
> > <rmannibucau@gmail.com <ma...@gmail.com>> wrote:
> >
> > +1 (same tests than for take #1)
> >
> > Le dim. 17 juin 2018 07:18, Jean-Baptiste Onofré <jb@nanthrax.net
> > <ma...@nanthrax.net>> a écrit :
> >
> > 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 <http://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 <http://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
> >
> > --
> > Got feedback? go/pabloem-feedback
> <https://goto.google.com/pabloem-feedback>
>
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
Re: [VOTE] Apache Beam, version 2.5.0, release candidate #2
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
s/add/had/g
On 17/06/2018 19:32, Pablo Estrada wrote:
> Going to https://github.com/apache/beam/tree/v2.5.0-RC2 gives me a 404
> error. May need to push the label?
> Best
> -P.
>
> On Sun, Jun 17, 2018 at 1:15 AM Romain Manni-Bucau
> <rmannibucau@gmail.com <ma...@gmail.com>> wrote:
>
> +1 (same tests than for take #1)
>
> Le dim. 17 juin 2018 07:18, Jean-Baptiste Onofré <jb@nanthrax.net
> <ma...@nanthrax.net>> a écrit :
>
> 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 <http://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 <http://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
>
> --
> Got feedback? go/pabloem-feedback
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: [VOTE] Apache Beam, version 2.5.0, release candidate #2
Posted by Yifan Zou <yi...@google.com>.
+1
Python quick-start and mobile-gaming on core runners passed.
On Sun, Jun 17, 2018 at 10:32 AM Pablo Estrada <pa...@google.com> wrote:
> Going to https://github.com/apache/beam/tree/v2.5.0-RC2 gives me a 404
> error. May need to push the label?
> Best
> -P.
>
> On Sun, Jun 17, 2018 at 1:15 AM Romain Manni-Bucau <rm...@gmail.com>
> wrote:
>
>> +1 (same tests than for take #1)
>>
>> Le dim. 17 juin 2018 07:18, Jean-Baptiste Onofré <jb...@nanthrax.net> a
>> écrit :
>>
>>> 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
>>>
>> --
> Got feedback? go/pabloem-feedback
> <https://goto.google.com/pabloem-feedback>
>
Re: [VOTE] Apache Beam, version 2.5.0, release candidate #2
Posted by Pablo Estrada <pa...@google.com>.
Going to https://github.com/apache/beam/tree/v2.5.0-RC2 gives me a 404
error. May need to push the label?
Best
-P.
On Sun, Jun 17, 2018 at 1:15 AM Romain Manni-Bucau <rm...@gmail.com>
wrote:
> +1 (same tests than for take #1)
>
> Le dim. 17 juin 2018 07:18, Jean-Baptiste Onofré <jb...@nanthrax.net> a
> écrit :
>
>> 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
>>
> --
Got feedback? go/pabloem-feedback
Re: [VOTE] Apache Beam, version 2.5.0, release candidate #2
Posted by Romain Manni-Bucau <rm...@gmail.com>.
+1 (same tests than for take #1)
Le dim. 17 juin 2018 07:18, Jean-Baptiste Onofré <jb...@nanthrax.net> a écrit :
> 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
>
Re: [VOTE] Apache Beam, version 2.5.0, release candidate #2
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
No problem at all, I'm just reviewing to close the vote ;)
Regards
JB
On 22/06/2018 11:44, Pablo Estrada wrote:
> Yes, sorry about the confusion!
> -P.
>
> On Fri, Jun 22, 2018, 3:06 AM Jean-Baptiste Onofré <jb@nanthrax.net
> <ma...@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 <http://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 <http://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é
> jbonofre@apache.org <ma...@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
Posted by Pablo Estrada <pa...@google.com>.
Yes, sorry about the confusion!
-P.
On Fri, Jun 22, 2018, 3:06 AM Jean-Baptiste Onofré <jb...@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é
> jbonofre@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
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
+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é
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: [RESULT][VOTE] Apache Beam, version 2.5.0, release candidate #2
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Thanks !
Just landed in Beijing. I will do the announcement this morning (China time).
Regards
JB
Le 27 juin 2018 à 05:24, à 05:24, Ahmet Altay <al...@google.com> a écrit:
>Beam site pull request is merged.
>
>JB, please send release announcement whenever it is convenient for you.
>
>Thank you again!
>Ahmet
>
>On Mon, Jun 25, 2018 at 10:39 PM, Ahmet Altay <al...@google.com> wrote:
>
>> Thank you JB!
>>
>> On Mon, Jun 25, 2018 at 10:34 PM, Jean-Baptiste Onofré
><jb...@nanthrax.net>
>> wrote:
>>
>>> Hi,
>>>
>>> all has been deployed: pypi contains both zip and whl files,
>artifacts
>>> are on central and dist.apache.org.
>>>
>>> The only pending is the merge of the Beam site pull request (I
>launched
>>> a asfbot merge this morning).
>>>
>>> Regards
>>> JB
>>>
>>> On 25/06/2018 19:49, Ahmet Altay wrote:
>>> > JB, thank you for making this release happen.
>>> >
>>> > I noticed that python artifacts are not deployed to pypi yet.
>Would you
>>> > like me to do that?
>>> >
>>> > Thank you,
>>> > Ahmet
>>> >
>>> > On Sat, Jun 23, 2018 at 6:45 AM, Rafael Fernandez
><rfernand@google.com
>>> > <ma...@google.com>> wrote:
>>> >
>>> > Great news! Thanks so much to our Release Manager and
>everybody who
>>> > helped iron out the wrinkles!
>>> >
>>> > If you haven't seen it already, look for the thread
>"[PROPOSAL] Add
>>> > a blog post for Beam release 2.5.0
>>> > " [1]
>>> > in dev@ - Alexey Romanenko has put together a very nice
>summary of
>>> > all the good stuff in 2.5.0.
>>> >
>>> >
>>> > [1] https://lists.apache.org/thread.html/ae3284ca051b800b3e
>>> dd73ad0f7f62344e26d3957b46794149bf1fb2@%3Cdev.beam.apache.org%3E
>>> > <https://lists.apache.org/thread.html/ae3284ca051b800b3edd7
>>> 3ad0f7f62344e26d3957b46794149bf1fb2@%3Cdev.beam.apache.org%3E>
>>> >
>>> > "
>>> >
>>> > On Fri, Jun 22, 2018 at 8:33 PM Jean-Baptiste Onofré
>>> > <jb@nanthrax.net <ma...@nanthrax.net>> wrote:
>>> >
>>> > I meant August (not July) for next release cycle.
>>> >
>>> > Regards
>>> > JB
>>> >
>>> > On 23/06/2018 05:17, Jean-Baptiste Onofré wrote:
>>> > > Hi all,
>>> > >
>>> > > I'm happy to announce that we have unanimously approved
>this
>>> > release.
>>> > >
>>> > > There are 12 approving votes, 5 of which are binding:
>>> > > * Ahmet Altay
>>> > > * Jean-Baptiste Onofré
>>> > > * Lukasz Cwik
>>> > > * Reuven Lax
>>> > > * Robert Bradshaw
>>> > >
>>> > > There are no disapproving votes.
>>> > >
>>> > > I'm finalizing the release.
>>> > >
>>> > > Thanks everyone!
>>> > >
>>> > > The 2.6.0 release process is expected to begin in 6
>weeks. So
>>> > we should
>>> > > start the Jira triage on Saturday, 4th July and I would
>like
>>> > to start
>>> > > the release process on Tuesday 7th.
>>> > >
>>> > > 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 <http://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 <http://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?proj
>>> ectId=12319527&version=12342847
>>> >
><https://issues.apache.org/jira/secure/ReleaseNote.jspa?pro
>>> jectId=12319527&version=12342847>
>>> > >> [2] https://dist.apache.org/repos/dist/dev/beam/2.5.0/
>>> > <https://dist.apache.org/repos/dist/dev/beam/2.5.0/>
>>> > >> [3]
>https://dist.apache.org/repos/dist/release/beam/KEYS
>>> > <https://dist.apache.org/repos/dist/release/beam/KEYS>
>>> > >> [4]
>>> > https://repository.apache.org/content/repositories/orgap
>>> achebeam-1043/
>>> >
><https://repository.apache.org/content/repositories/orgapac
>>> hebeam-1043/>
>>> > >> [5] https://github.com/apache/beam/tree/v2.5.0-RC2
>>> > <https://github.com/apache/beam/tree/v2.5.0-RC2>
>>> > >> [6] https://github.com/apache/beam-site/pull/463
>>> > <https://github.com/apache/beam-site/pull/463>
>>> > >>
>>> > >
>>> >
>>> > --
>>> > Jean-Baptiste Onofré
>>> > jbonofre@apache.org <ma...@apache.org>
>>> > http://blog.nanthrax.net
>>> > Talend - http://www.talend.com
>>> >
>>> >
>>>
>>> --
>>> Jean-Baptiste Onofré
>>> jbonofre@apache.org
>>> http://blog.nanthrax.net
>>> Talend - http://www.talend.com
>>>
>>
>>
Re: [RESULT][VOTE] Apache Beam, version 2.5.0, release candidate #2
Posted by Ahmet Altay <al...@google.com>.
Beam site pull request is merged.
JB, please send release announcement whenever it is convenient for you.
Thank you again!
Ahmet
On Mon, Jun 25, 2018 at 10:39 PM, Ahmet Altay <al...@google.com> wrote:
> Thank you JB!
>
> On Mon, Jun 25, 2018 at 10:34 PM, Jean-Baptiste Onofré <jb...@nanthrax.net>
> wrote:
>
>> Hi,
>>
>> all has been deployed: pypi contains both zip and whl files, artifacts
>> are on central and dist.apache.org.
>>
>> The only pending is the merge of the Beam site pull request (I launched
>> a asfbot merge this morning).
>>
>> Regards
>> JB
>>
>> On 25/06/2018 19:49, Ahmet Altay wrote:
>> > JB, thank you for making this release happen.
>> >
>> > I noticed that python artifacts are not deployed to pypi yet. Would you
>> > like me to do that?
>> >
>> > Thank you,
>> > Ahmet
>> >
>> > On Sat, Jun 23, 2018 at 6:45 AM, Rafael Fernandez <rfernand@google.com
>> > <ma...@google.com>> wrote:
>> >
>> > Great news! Thanks so much to our Release Manager and everybody who
>> > helped iron out the wrinkles!
>> >
>> > If you haven't seen it already, look for the thread "[PROPOSAL] Add
>> > a blog post for Beam release 2.5.0
>> > " [1]
>> > in dev@ - Alexey Romanenko has put together a very nice summary of
>> > all the good stuff in 2.5.0.
>> >
>> >
>> > [1] https://lists.apache.org/thread.html/ae3284ca051b800b3e
>> dd73ad0f7f62344e26d3957b46794149bf1fb2@%3Cdev.beam.apache.org%3E
>> > <https://lists.apache.org/thread.html/ae3284ca051b800b3edd7
>> 3ad0f7f62344e26d3957b46794149bf1fb2@%3Cdev.beam.apache.org%3E>
>> >
>> > "
>> >
>> > On Fri, Jun 22, 2018 at 8:33 PM Jean-Baptiste Onofré
>> > <jb@nanthrax.net <ma...@nanthrax.net>> wrote:
>> >
>> > I meant August (not July) for next release cycle.
>> >
>> > Regards
>> > JB
>> >
>> > On 23/06/2018 05:17, Jean-Baptiste Onofré wrote:
>> > > Hi all,
>> > >
>> > > I'm happy to announce that we have unanimously approved this
>> > release.
>> > >
>> > > There are 12 approving votes, 5 of which are binding:
>> > > * Ahmet Altay
>> > > * Jean-Baptiste Onofré
>> > > * Lukasz Cwik
>> > > * Reuven Lax
>> > > * Robert Bradshaw
>> > >
>> > > There are no disapproving votes.
>> > >
>> > > I'm finalizing the release.
>> > >
>> > > Thanks everyone!
>> > >
>> > > The 2.6.0 release process is expected to begin in 6 weeks. So
>> > we should
>> > > start the Jira triage on Saturday, 4th July and I would like
>> > to start
>> > > the release process on Tuesday 7th.
>> > >
>> > > 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 <http://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 <http://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?proj
>> ectId=12319527&version=12342847
>> > <https://issues.apache.org/jira/secure/ReleaseNote.jspa?pro
>> jectId=12319527&version=12342847>
>> > >> [2] https://dist.apache.org/repos/dist/dev/beam/2.5.0/
>> > <https://dist.apache.org/repos/dist/dev/beam/2.5.0/>
>> > >> [3] https://dist.apache.org/repos/dist/release/beam/KEYS
>> > <https://dist.apache.org/repos/dist/release/beam/KEYS>
>> > >> [4]
>> > https://repository.apache.org/content/repositories/orgap
>> achebeam-1043/
>> > <https://repository.apache.org/content/repositories/orgapac
>> hebeam-1043/>
>> > >> [5] https://github.com/apache/beam/tree/v2.5.0-RC2
>> > <https://github.com/apache/beam/tree/v2.5.0-RC2>
>> > >> [6] https://github.com/apache/beam-site/pull/463
>> > <https://github.com/apache/beam-site/pull/463>
>> > >>
>> > >
>> >
>> > --
>> > Jean-Baptiste Onofré
>> > jbonofre@apache.org <ma...@apache.org>
>> > http://blog.nanthrax.net
>> > Talend - http://www.talend.com
>> >
>> >
>>
>> --
>> Jean-Baptiste Onofré
>> jbonofre@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
>
>
Re: [RESULT][VOTE] Apache Beam, version 2.5.0, release candidate #2
Posted by Ahmet Altay <al...@google.com>.
Thank you JB!
On Mon, Jun 25, 2018 at 10:34 PM, Jean-Baptiste Onofré <jb...@nanthrax.net>
wrote:
> Hi,
>
> all has been deployed: pypi contains both zip and whl files, artifacts
> are on central and dist.apache.org.
>
> The only pending is the merge of the Beam site pull request (I launched
> a asfbot merge this morning).
>
> Regards
> JB
>
> On 25/06/2018 19:49, Ahmet Altay wrote:
> > JB, thank you for making this release happen.
> >
> > I noticed that python artifacts are not deployed to pypi yet. Would you
> > like me to do that?
> >
> > Thank you,
> > Ahmet
> >
> > On Sat, Jun 23, 2018 at 6:45 AM, Rafael Fernandez <rfernand@google.com
> > <ma...@google.com>> wrote:
> >
> > Great news! Thanks so much to our Release Manager and everybody who
> > helped iron out the wrinkles!
> >
> > If you haven't seen it already, look for the thread "[PROPOSAL] Add
> > a blog post for Beam release 2.5.0
> > " [1]
> > in dev@ - Alexey Romanenko has put together a very nice summary of
> > all the good stuff in 2.5.0.
> >
> >
> > [1] https://lists.apache.org/thread.html/
> ae3284ca051b800b3edd73ad0f7f62344e26d3957b46794149bf1fb2@%
> 3Cdev.beam.apache.org%3E
> > <https://lists.apache.org/thread.html/ae3284ca051b800b3edd73ad0f7f62
> 344e26d3957b46794149bf1fb2@%3Cdev.beam.apache.org%3E>
> >
> > "
> >
> > On Fri, Jun 22, 2018 at 8:33 PM Jean-Baptiste Onofré
> > <jb@nanthrax.net <ma...@nanthrax.net>> wrote:
> >
> > I meant August (not July) for next release cycle.
> >
> > Regards
> > JB
> >
> > On 23/06/2018 05:17, Jean-Baptiste Onofré wrote:
> > > Hi all,
> > >
> > > I'm happy to announce that we have unanimously approved this
> > release.
> > >
> > > There are 12 approving votes, 5 of which are binding:
> > > * Ahmet Altay
> > > * Jean-Baptiste Onofré
> > > * Lukasz Cwik
> > > * Reuven Lax
> > > * Robert Bradshaw
> > >
> > > There are no disapproving votes.
> > >
> > > I'm finalizing the release.
> > >
> > > Thanks everyone!
> > >
> > > The 2.6.0 release process is expected to begin in 6 weeks. So
> > we should
> > > start the Jira triage on Saturday, 4th July and I would like
> > to start
> > > the release process on Tuesday 7th.
> > >
> > > 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 <http://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 <http://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
> > <https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12319527&version=12342847>
> > >> [2] https://dist.apache.org/repos/dist/dev/beam/2.5.0/
> > <https://dist.apache.org/repos/dist/dev/beam/2.5.0/>
> > >> [3] https://dist.apache.org/repos/dist/release/beam/KEYS
> > <https://dist.apache.org/repos/dist/release/beam/KEYS>
> > >> [4]
> > https://repository.apache.org/content/repositories/
> orgapachebeam-1043/
> > <https://repository.apache.org/content/repositories/
> orgapachebeam-1043/>
> > >> [5] https://github.com/apache/beam/tree/v2.5.0-RC2
> > <https://github.com/apache/beam/tree/v2.5.0-RC2>
> > >> [6] https://github.com/apache/beam-site/pull/463
> > <https://github.com/apache/beam-site/pull/463>
> > >>
> > >
> >
> > --
> > Jean-Baptiste Onofré
> > jbonofre@apache.org <ma...@apache.org>
> > http://blog.nanthrax.net
> > Talend - http://www.talend.com
> >
> >
>
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
Re: [RESULT][VOTE] Apache Beam, version 2.5.0, release candidate #2
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi,
all has been deployed: pypi contains both zip and whl files, artifacts
are on central and dist.apache.org.
The only pending is the merge of the Beam site pull request (I launched
a asfbot merge this morning).
Regards
JB
On 25/06/2018 19:49, Ahmet Altay wrote:
> JB, thank you for making this release happen.
>
> I noticed that python artifacts are not deployed to pypi yet. Would you
> like me to do that?
>
> Thank you,
> Ahmet
>
> On Sat, Jun 23, 2018 at 6:45 AM, Rafael Fernandez <rfernand@google.com
> <ma...@google.com>> wrote:
>
> Great news! Thanks so much to our Release Manager and everybody who
> helped iron out the wrinkles!
>
> If you haven't seen it already, look for the thread "[PROPOSAL] Add
> a blog post for Beam release 2.5.0
> " [1]
> in dev@ - Alexey Romanenko has put together a very nice summary of
> all the good stuff in 2.5.0.
>
>
> [1] https://lists.apache.org/thread.html/ae3284ca051b800b3edd73ad0f7f62344e26d3957b46794149bf1fb2@%3Cdev.beam.apache.org%3E
> <https://lists.apache.org/thread.html/ae3284ca051b800b3edd73ad0f7f62344e26d3957b46794149bf1fb2@%3Cdev.beam.apache.org%3E>
>
> "
>
> On Fri, Jun 22, 2018 at 8:33 PM Jean-Baptiste Onofré
> <jb@nanthrax.net <ma...@nanthrax.net>> wrote:
>
> I meant August (not July) for next release cycle.
>
> Regards
> JB
>
> On 23/06/2018 05:17, Jean-Baptiste Onofré wrote:
> > Hi all,
> >
> > I'm happy to announce that we have unanimously approved this
> release.
> >
> > There are 12 approving votes, 5 of which are binding:
> > * Ahmet Altay
> > * Jean-Baptiste Onofré
> > * Lukasz Cwik
> > * Reuven Lax
> > * Robert Bradshaw
> >
> > There are no disapproving votes.
> >
> > I'm finalizing the release.
> >
> > Thanks everyone!
> >
> > The 2.6.0 release process is expected to begin in 6 weeks. So
> we should
> > start the Jira triage on Saturday, 4th July and I would like
> to start
> > the release process on Tuesday 7th.
> >
> > 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 <http://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 <http://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
> <https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527&version=12342847>
> >> [2] https://dist.apache.org/repos/dist/dev/beam/2.5.0/
> <https://dist.apache.org/repos/dist/dev/beam/2.5.0/>
> >> [3] https://dist.apache.org/repos/dist/release/beam/KEYS
> <https://dist.apache.org/repos/dist/release/beam/KEYS>
> >> [4]
> https://repository.apache.org/content/repositories/orgapachebeam-1043/
> <https://repository.apache.org/content/repositories/orgapachebeam-1043/>
> >> [5] https://github.com/apache/beam/tree/v2.5.0-RC2
> <https://github.com/apache/beam/tree/v2.5.0-RC2>
> >> [6] https://github.com/apache/beam-site/pull/463
> <https://github.com/apache/beam-site/pull/463>
> >>
> >
>
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org <ma...@apache.org>
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: [RESULT][VOTE] Apache Beam, version 2.5.0, release candidate #2
Posted by Rafael Fernandez <rf...@google.com>.
Neat! Thanks! (No guesswork! Just look at the calendar! :D)
On Mon, Jun 25, 2018 at 2:47 PM Kenneth Knowles <kl...@google.com> wrote:
> I quickly put together https://s.apache.org/beam-release-calendar. I
> started from the day that the 2.5.0 release branch was created.
>
> Kenn
>
> On Mon, Jun 25, 2018 at 2:10 PM Lukasz Cwik <lc...@google.com> wrote:
>
>> If our release process is taking longer then 6 weeks, we should probably
>> start the next release since we expect that it will take a long time as
>> well even though the prior one is not yet finished. This will help get to
>> an average of one release every 6 weeks.
>>
>> On Mon, Jun 25, 2018 at 1:52 PM Chamikara Jayalath <ch...@google.com>
>> wrote:
>>
>>> I think the idea was to include a 6 weeks worth of change diff in
>>> subsequent releases. So cutting the 2.6.0 release branch 6 weeks from the
>>> date 2.5.0 branch was cut sounds proper to me. I think we should
>>> consistently cut release branches every six weeks even though some of the
>>> releases might take longer than expected (hopefully not six weeks :)).
>>>
>>> - Cham
>>>
>>> On Mon, Jun 25, 2018 at 12:54 PM Andrew Pilloud <ap...@google.com>
>>> wrote:
>>>
>>>> If I recall from the 2.4 discussion, the 2.5 branch should have been
>>>> cut in late April. It was cut ~5 weeks late. Keeping to the 6 week release
>>>> cadence, we are already late cutting the 2.6 release branch, which should
>>>> be cut immediately. Then 2.7 should be cut in mid July.
>>>>
>>>> Andrew
>>>>
>>>> On Mon, Jun 25, 2018 at 12:32 PM Kenneth Knowles <kl...@google.com>
>>>> wrote:
>>>>
>>>>> Specifically, I mean that since we cut release-2.5.0 branch on Jun 6
>>>>> we would cut release-2.6.0 on July 18.
>>>>>
>>>>> This time around, we should cut first, cherry-pick second.
>>>>>
>>>>> Kenn
>>>>>
>>>>> On Mon, Jun 25, 2018 at 12:21 PM Jean-Baptiste Onofré <jb...@nanthrax.net>
>>>>> wrote:
>>>>>
>>>>>> It makes sense.
>>>>>>
>>>>>> So, I will start the 2.6.0 process on July 17.
>>>>>>
>>>>>> Regards
>>>>>> JB
>>>>>>
>>>>>> On 25/06/2018 20:47, Alan Myrvold wrote:
>>>>>> > It would be a more predictable cadence to have a consistent timing
>>>>>> > between when the release branches are cut, and not when the release
>>>>>> is
>>>>>> > published.
>>>>>> >
>>>>>> > If 2.5.0 was cut on June 5, then 2.6.0 could be cut July 17?
>>>>>> >
>>>>>> > On Mon, Jun 25, 2018 at 10:57 AM Ahmet Altay <altay@google.com
>>>>>> > <ma...@google.com>> wrote:
>>>>>> >
>>>>>> >
>>>>>> >
>>>>>> > On Mon, Jun 25, 2018 at 10:49 AM, Ahmet Altay <altay@google.com
>>>>>> > <ma...@google.com>> wrote:
>>>>>> >
>>>>>> > JB, thank you for making this release happen.
>>>>>> >
>>>>>> > I noticed that python artifacts are not deployed to pypi
>>>>>> yet.
>>>>>> > Would you like me to do that?
>>>>>> >
>>>>>> > Thank you,
>>>>>> > Ahmet
>>>>>> >
>>>>>> > On Sat, Jun 23, 2018 at 6:45 AM, Rafael Fernandez
>>>>>> > <rfernand@google.com <ma...@google.com>> wrote:
>>>>>> >
>>>>>> > Great news! Thanks so much to our Release Manager and
>>>>>> > everybody who helped iron out the wrinkles!
>>>>>> >
>>>>>> > If you haven't seen it already, look for the thread
>>>>>> > "[PROPOSAL] Add a blog post for Beam release 2.5.0
>>>>>> > " [1]
>>>>>> > in dev@ - Alexey Romanenko has put together a very
>>>>>> nice
>>>>>> > summary of all the good stuff in 2.5.0.
>>>>>> >
>>>>>> >
>>>>>> > [1]
>>>>>> https://lists.apache.org/thread.html/ae3284ca051b800b3edd73ad0f7f62344e26d3957b46794149bf1fb2@%3Cdev.beam.apache.org%3E
>>>>>>
>>>>>> >
>>>>>> > "
>>>>>> >
>>>>>> > On Fri, Jun 22, 2018 at 8:33 PM Jean-Baptiste Onofré
>>>>>> > <jb@nanthrax.net <ma...@nanthrax.net>> wrote:
>>>>>> >
>>>>>> > I meant August (not July) for next release cycle.
>>>>>> >
>>>>>> > Regards
>>>>>> > JB
>>>>>> >
>>>>>> > On 23/06/2018 05:17, Jean-Baptiste Onofré wrote:
>>>>>> > > Hi all,
>>>>>> > >
>>>>>> > > I'm happy to announce that we have unanimously
>>>>>> > approved this release.
>>>>>> > >
>>>>>> > > There are 12 approving votes, 5 of which are
>>>>>> binding:
>>>>>> > > * Ahmet Altay
>>>>>> > > * Jean-Baptiste Onofré
>>>>>> > > * Lukasz Cwik
>>>>>> > > * Reuven Lax
>>>>>> > > * Robert Bradshaw
>>>>>> > >
>>>>>> > > There are no disapproving votes.
>>>>>> > >
>>>>>> > > I'm finalizing the release.
>>>>>> > >
>>>>>> > > Thanks everyone!
>>>>>> > >
>>>>>> > > The 2.6.0 release process is expected to begin in
>>>>>> 6
>>>>>> > weeks. So we should
>>>>>> > > start the Jira triage on Saturday, 4th July and I
>>>>>> > would like to start
>>>>>> > > the release process on Tuesday 7th.
>>>>>> >
>>>>>> >
>>>>>> > My understanding was that there will be a release every 6
>>>>>> weeks. It
>>>>>> > seems like with this plan (to start release process on August
>>>>>> 7),
>>>>>> > the understanding is that we will have 6 weeks between a
>>>>>> release is
>>>>>> > out and the start of the next release process. My take is, we
>>>>>> need
>>>>>> > to have a user centric view and a make promise to release every
>>>>>> X
>>>>>> > weeks. If X=6 is not sustainable we can discuss. However,
>>>>>> having X
>>>>>> > weeks in between a release cut and release start will result in
>>>>>> > unpredictable release dates.
>>>>>> >
>>>>>> > What do you think?
>>>>>> >
>>>>>> >
>>>>>> > >
>>>>>> > > 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 <http://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 <http://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é
>>>>>> > jbonofre@apache.org <ma...@apache.org>
>>>>>> > http://blog.nanthrax.net
>>>>>> > Talend - http://www.talend.com
>>>>>> >
>>>>>> >
>>>>>> >
>>>>>>
>>>>>> --
>>>>>> Jean-Baptiste Onofré
>>>>>> jbonofre@apache.org
>>>>>> http://blog.nanthrax.net
>>>>>> Talend - http://www.talend.com
>>>>>>
>>>>>
Re: [RESULT][VOTE] Apache Beam, version 2.5.0, release candidate #2
Posted by Kenneth Knowles <kl...@google.com>.
I quickly put together https://s.apache.org/beam-release-calendar. I
started from the day that the 2.5.0 release branch was created.
Kenn
On Mon, Jun 25, 2018 at 2:10 PM Lukasz Cwik <lc...@google.com> wrote:
> If our release process is taking longer then 6 weeks, we should probably
> start the next release since we expect that it will take a long time as
> well even though the prior one is not yet finished. This will help get to
> an average of one release every 6 weeks.
>
> On Mon, Jun 25, 2018 at 1:52 PM Chamikara Jayalath <ch...@google.com>
> wrote:
>
>> I think the idea was to include a 6 weeks worth of change diff in
>> subsequent releases. So cutting the 2.6.0 release branch 6 weeks from the
>> date 2.5.0 branch was cut sounds proper to me. I think we should
>> consistently cut release branches every six weeks even though some of the
>> releases might take longer than expected (hopefully not six weeks :)).
>>
>> - Cham
>>
>> On Mon, Jun 25, 2018 at 12:54 PM Andrew Pilloud <ap...@google.com>
>> wrote:
>>
>>> If I recall from the 2.4 discussion, the 2.5 branch should have been cut
>>> in late April. It was cut ~5 weeks late. Keeping to the 6 week release
>>> cadence, we are already late cutting the 2.6 release branch, which should
>>> be cut immediately. Then 2.7 should be cut in mid July.
>>>
>>> Andrew
>>>
>>> On Mon, Jun 25, 2018 at 12:32 PM Kenneth Knowles <kl...@google.com> wrote:
>>>
>>>> Specifically, I mean that since we cut release-2.5.0 branch on Jun 6 we
>>>> would cut release-2.6.0 on July 18.
>>>>
>>>> This time around, we should cut first, cherry-pick second.
>>>>
>>>> Kenn
>>>>
>>>> On Mon, Jun 25, 2018 at 12:21 PM Jean-Baptiste Onofré <jb...@nanthrax.net>
>>>> wrote:
>>>>
>>>>> It makes sense.
>>>>>
>>>>> So, I will start the 2.6.0 process on July 17.
>>>>>
>>>>> Regards
>>>>> JB
>>>>>
>>>>> On 25/06/2018 20:47, Alan Myrvold wrote:
>>>>> > It would be a more predictable cadence to have a consistent timing
>>>>> > between when the release branches are cut, and not when the release
>>>>> is
>>>>> > published.
>>>>> >
>>>>> > If 2.5.0 was cut on June 5, then 2.6.0 could be cut July 17?
>>>>> >
>>>>> > On Mon, Jun 25, 2018 at 10:57 AM Ahmet Altay <altay@google.com
>>>>> > <ma...@google.com>> wrote:
>>>>> >
>>>>> >
>>>>> >
>>>>> > On Mon, Jun 25, 2018 at 10:49 AM, Ahmet Altay <altay@google.com
>>>>> > <ma...@google.com>> wrote:
>>>>> >
>>>>> > JB, thank you for making this release happen.
>>>>> >
>>>>> > I noticed that python artifacts are not deployed to pypi yet.
>>>>> > Would you like me to do that?
>>>>> >
>>>>> > Thank you,
>>>>> > Ahmet
>>>>> >
>>>>> > On Sat, Jun 23, 2018 at 6:45 AM, Rafael Fernandez
>>>>> > <rfernand@google.com <ma...@google.com>> wrote:
>>>>> >
>>>>> > Great news! Thanks so much to our Release Manager and
>>>>> > everybody who helped iron out the wrinkles!
>>>>> >
>>>>> > If you haven't seen it already, look for the thread
>>>>> > "[PROPOSAL] Add a blog post for Beam release 2.5.0
>>>>> > " [1]
>>>>> > in dev@ - Alexey Romanenko has put together a very nice
>>>>> > summary of all the good stuff in 2.5.0.
>>>>> >
>>>>> >
>>>>> > [1]
>>>>> https://lists.apache.org/thread.html/ae3284ca051b800b3edd73ad0f7f62344e26d3957b46794149bf1fb2@%3Cdev.beam.apache.org%3E
>>>>>
>>>>> >
>>>>> > "
>>>>> >
>>>>> > On Fri, Jun 22, 2018 at 8:33 PM Jean-Baptiste Onofré
>>>>> > <jb@nanthrax.net <ma...@nanthrax.net>> wrote:
>>>>> >
>>>>> > I meant August (not July) for next release cycle.
>>>>> >
>>>>> > Regards
>>>>> > JB
>>>>> >
>>>>> > On 23/06/2018 05:17, Jean-Baptiste Onofré wrote:
>>>>> > > Hi all,
>>>>> > >
>>>>> > > I'm happy to announce that we have unanimously
>>>>> > approved this release.
>>>>> > >
>>>>> > > There are 12 approving votes, 5 of which are
>>>>> binding:
>>>>> > > * Ahmet Altay
>>>>> > > * Jean-Baptiste Onofré
>>>>> > > * Lukasz Cwik
>>>>> > > * Reuven Lax
>>>>> > > * Robert Bradshaw
>>>>> > >
>>>>> > > There are no disapproving votes.
>>>>> > >
>>>>> > > I'm finalizing the release.
>>>>> > >
>>>>> > > Thanks everyone!
>>>>> > >
>>>>> > > The 2.6.0 release process is expected to begin in 6
>>>>> > weeks. So we should
>>>>> > > start the Jira triage on Saturday, 4th July and I
>>>>> > would like to start
>>>>> > > the release process on Tuesday 7th.
>>>>> >
>>>>> >
>>>>> > My understanding was that there will be a release every 6 weeks.
>>>>> It
>>>>> > seems like with this plan (to start release process on August 7),
>>>>> > the understanding is that we will have 6 weeks between a release
>>>>> is
>>>>> > out and the start of the next release process. My take is, we
>>>>> need
>>>>> > to have a user centric view and a make promise to release every X
>>>>> > weeks. If X=6 is not sustainable we can discuss. However, having
>>>>> X
>>>>> > weeks in between a release cut and release start will result in
>>>>> > unpredictable release dates.
>>>>> >
>>>>> > What do you think?
>>>>> >
>>>>> >
>>>>> > >
>>>>> > > 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 <http://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 <http://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é
>>>>> > jbonofre@apache.org <ma...@apache.org>
>>>>> > http://blog.nanthrax.net
>>>>> > Talend - http://www.talend.com
>>>>> >
>>>>> >
>>>>> >
>>>>>
>>>>> --
>>>>> Jean-Baptiste Onofré
>>>>> jbonofre@apache.org
>>>>> http://blog.nanthrax.net
>>>>> Talend - http://www.talend.com
>>>>>
>>>>
Re: [RESULT][VOTE] Apache Beam, version 2.5.0, release candidate #2
Posted by Lukasz Cwik <lc...@google.com>.
If our release process is taking longer then 6 weeks, we should probably
start the next release since we expect that it will take a long time as
well even though the prior one is not yet finished. This will help get to
an average of one release every 6 weeks.
On Mon, Jun 25, 2018 at 1:52 PM Chamikara Jayalath <ch...@google.com>
wrote:
> I think the idea was to include a 6 weeks worth of change diff in
> subsequent releases. So cutting the 2.6.0 release branch 6 weeks from the
> date 2.5.0 branch was cut sounds proper to me. I think we should
> consistently cut release branches every six weeks even though some of the
> releases might take longer than expected (hopefully not six weeks :)).
>
> - Cham
>
> On Mon, Jun 25, 2018 at 12:54 PM Andrew Pilloud <ap...@google.com>
> wrote:
>
>> If I recall from the 2.4 discussion, the 2.5 branch should have been cut
>> in late April. It was cut ~5 weeks late. Keeping to the 6 week release
>> cadence, we are already late cutting the 2.6 release branch, which should
>> be cut immediately. Then 2.7 should be cut in mid July.
>>
>> Andrew
>>
>> On Mon, Jun 25, 2018 at 12:32 PM Kenneth Knowles <kl...@google.com> wrote:
>>
>>> Specifically, I mean that since we cut release-2.5.0 branch on Jun 6 we
>>> would cut release-2.6.0 on July 18.
>>>
>>> This time around, we should cut first, cherry-pick second.
>>>
>>> Kenn
>>>
>>> On Mon, Jun 25, 2018 at 12:21 PM Jean-Baptiste Onofré <jb...@nanthrax.net>
>>> wrote:
>>>
>>>> It makes sense.
>>>>
>>>> So, I will start the 2.6.0 process on July 17.
>>>>
>>>> Regards
>>>> JB
>>>>
>>>> On 25/06/2018 20:47, Alan Myrvold wrote:
>>>> > It would be a more predictable cadence to have a consistent timing
>>>> > between when the release branches are cut, and not when the release is
>>>> > published.
>>>> >
>>>> > If 2.5.0 was cut on June 5, then 2.6.0 could be cut July 17?
>>>> >
>>>> > On Mon, Jun 25, 2018 at 10:57 AM Ahmet Altay <altay@google.com
>>>> > <ma...@google.com>> wrote:
>>>> >
>>>> >
>>>> >
>>>> > On Mon, Jun 25, 2018 at 10:49 AM, Ahmet Altay <altay@google.com
>>>> > <ma...@google.com>> wrote:
>>>> >
>>>> > JB, thank you for making this release happen.
>>>> >
>>>> > I noticed that python artifacts are not deployed to pypi yet.
>>>> > Would you like me to do that?
>>>> >
>>>> > Thank you,
>>>> > Ahmet
>>>> >
>>>> > On Sat, Jun 23, 2018 at 6:45 AM, Rafael Fernandez
>>>> > <rfernand@google.com <ma...@google.com>> wrote:
>>>> >
>>>> > Great news! Thanks so much to our Release Manager and
>>>> > everybody who helped iron out the wrinkles!
>>>> >
>>>> > If you haven't seen it already, look for the thread
>>>> > "[PROPOSAL] Add a blog post for Beam release 2.5.0
>>>> > " [1]
>>>> > in dev@ - Alexey Romanenko has put together a very nice
>>>> > summary of all the good stuff in 2.5.0.
>>>> >
>>>> >
>>>> > [1]
>>>> https://lists.apache.org/thread.html/ae3284ca051b800b3edd73ad0f7f62344e26d3957b46794149bf1fb2@%3Cdev.beam.apache.org%3E
>>>>
>>>> >
>>>> > "
>>>> >
>>>> > On Fri, Jun 22, 2018 at 8:33 PM Jean-Baptiste Onofré
>>>> > <jb@nanthrax.net <ma...@nanthrax.net>> wrote:
>>>> >
>>>> > I meant August (not July) for next release cycle.
>>>> >
>>>> > Regards
>>>> > JB
>>>> >
>>>> > On 23/06/2018 05:17, Jean-Baptiste Onofré wrote:
>>>> > > Hi all,
>>>> > >
>>>> > > I'm happy to announce that we have unanimously
>>>> > approved this release.
>>>> > >
>>>> > > There are 12 approving votes, 5 of which are
>>>> binding:
>>>> > > * Ahmet Altay
>>>> > > * Jean-Baptiste Onofré
>>>> > > * Lukasz Cwik
>>>> > > * Reuven Lax
>>>> > > * Robert Bradshaw
>>>> > >
>>>> > > There are no disapproving votes.
>>>> > >
>>>> > > I'm finalizing the release.
>>>> > >
>>>> > > Thanks everyone!
>>>> > >
>>>> > > The 2.6.0 release process is expected to begin in 6
>>>> > weeks. So we should
>>>> > > start the Jira triage on Saturday, 4th July and I
>>>> > would like to start
>>>> > > the release process on Tuesday 7th.
>>>> >
>>>> >
>>>> > My understanding was that there will be a release every 6 weeks.
>>>> It
>>>> > seems like with this plan (to start release process on August 7),
>>>> > the understanding is that we will have 6 weeks between a release
>>>> is
>>>> > out and the start of the next release process. My take is, we need
>>>> > to have a user centric view and a make promise to release every X
>>>> > weeks. If X=6 is not sustainable we can discuss. However, having X
>>>> > weeks in between a release cut and release start will result in
>>>> > unpredictable release dates.
>>>> >
>>>> > What do you think?
>>>> >
>>>> >
>>>> > >
>>>> > > 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 <http://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 <http://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é
>>>> > jbonofre@apache.org <ma...@apache.org>
>>>> > http://blog.nanthrax.net
>>>> > Talend - http://www.talend.com
>>>> >
>>>> >
>>>> >
>>>>
>>>> --
>>>> Jean-Baptiste Onofré
>>>> jbonofre@apache.org
>>>> http://blog.nanthrax.net
>>>> Talend - http://www.talend.com
>>>>
>>>
Re: [RESULT][VOTE] Apache Beam, version 2.5.0, release candidate #2
Posted by Chamikara Jayalath <ch...@google.com>.
I think the idea was to include a 6 weeks worth of change diff in
subsequent releases. So cutting the 2.6.0 release branch 6 weeks from the
date 2.5.0 branch was cut sounds proper to me. I think we should
consistently cut release branches every six weeks even though some of the
releases might take longer than expected (hopefully not six weeks :)).
- Cham
On Mon, Jun 25, 2018 at 12:54 PM Andrew Pilloud <ap...@google.com> wrote:
> If I recall from the 2.4 discussion, the 2.5 branch should have been cut
> in late April. It was cut ~5 weeks late. Keeping to the 6 week release
> cadence, we are already late cutting the 2.6 release branch, which should
> be cut immediately. Then 2.7 should be cut in mid July.
>
> Andrew
>
> On Mon, Jun 25, 2018 at 12:32 PM Kenneth Knowles <kl...@google.com> wrote:
>
>> Specifically, I mean that since we cut release-2.5.0 branch on Jun 6 we
>> would cut release-2.6.0 on July 18.
>>
>> This time around, we should cut first, cherry-pick second.
>>
>> Kenn
>>
>> On Mon, Jun 25, 2018 at 12:21 PM Jean-Baptiste Onofré <jb...@nanthrax.net>
>> wrote:
>>
>>> It makes sense.
>>>
>>> So, I will start the 2.6.0 process on July 17.
>>>
>>> Regards
>>> JB
>>>
>>> On 25/06/2018 20:47, Alan Myrvold wrote:
>>> > It would be a more predictable cadence to have a consistent timing
>>> > between when the release branches are cut, and not when the release is
>>> > published.
>>> >
>>> > If 2.5.0 was cut on June 5, then 2.6.0 could be cut July 17?
>>> >
>>> > On Mon, Jun 25, 2018 at 10:57 AM Ahmet Altay <altay@google.com
>>> > <ma...@google.com>> wrote:
>>> >
>>> >
>>> >
>>> > On Mon, Jun 25, 2018 at 10:49 AM, Ahmet Altay <altay@google.com
>>> > <ma...@google.com>> wrote:
>>> >
>>> > JB, thank you for making this release happen.
>>> >
>>> > I noticed that python artifacts are not deployed to pypi yet.
>>> > Would you like me to do that?
>>> >
>>> > Thank you,
>>> > Ahmet
>>> >
>>> > On Sat, Jun 23, 2018 at 6:45 AM, Rafael Fernandez
>>> > <rfernand@google.com <ma...@google.com>> wrote:
>>> >
>>> > Great news! Thanks so much to our Release Manager and
>>> > everybody who helped iron out the wrinkles!
>>> >
>>> > If you haven't seen it already, look for the thread
>>> > "[PROPOSAL] Add a blog post for Beam release 2.5.0
>>> > " [1]
>>> > in dev@ - Alexey Romanenko has put together a very nice
>>> > summary of all the good stuff in 2.5.0.
>>> >
>>> >
>>> > [1]
>>> https://lists.apache.org/thread.html/ae3284ca051b800b3edd73ad0f7f62344e26d3957b46794149bf1fb2@%3Cdev.beam.apache.org%3E
>>>
>>> >
>>> > "
>>> >
>>> > On Fri, Jun 22, 2018 at 8:33 PM Jean-Baptiste Onofré
>>> > <jb@nanthrax.net <ma...@nanthrax.net>> wrote:
>>> >
>>> > I meant August (not July) for next release cycle.
>>> >
>>> > Regards
>>> > JB
>>> >
>>> > On 23/06/2018 05:17, Jean-Baptiste Onofré wrote:
>>> > > Hi all,
>>> > >
>>> > > I'm happy to announce that we have unanimously
>>> > approved this release.
>>> > >
>>> > > There are 12 approving votes, 5 of which are binding:
>>> > > * Ahmet Altay
>>> > > * Jean-Baptiste Onofré
>>> > > * Lukasz Cwik
>>> > > * Reuven Lax
>>> > > * Robert Bradshaw
>>> > >
>>> > > There are no disapproving votes.
>>> > >
>>> > > I'm finalizing the release.
>>> > >
>>> > > Thanks everyone!
>>> > >
>>> > > The 2.6.0 release process is expected to begin in 6
>>> > weeks. So we should
>>> > > start the Jira triage on Saturday, 4th July and I
>>> > would like to start
>>> > > the release process on Tuesday 7th.
>>> >
>>> >
>>> > My understanding was that there will be a release every 6 weeks. It
>>> > seems like with this plan (to start release process on August 7),
>>> > the understanding is that we will have 6 weeks between a release is
>>> > out and the start of the next release process. My take is, we need
>>> > to have a user centric view and a make promise to release every X
>>> > weeks. If X=6 is not sustainable we can discuss. However, having X
>>> > weeks in between a release cut and release start will result in
>>> > unpredictable release dates.
>>> >
>>> > What do you think?
>>> >
>>> >
>>> > >
>>> > > 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 <http://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 <http://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é
>>> > jbonofre@apache.org <ma...@apache.org>
>>> > http://blog.nanthrax.net
>>> > Talend - http://www.talend.com
>>> >
>>> >
>>> >
>>>
>>> --
>>> Jean-Baptiste Onofré
>>> jbonofre@apache.org
>>> http://blog.nanthrax.net
>>> Talend - http://www.talend.com
>>>
>>
Re: [RESULT][VOTE] Apache Beam, version 2.5.0, release candidate #2
Posted by Andrew Pilloud <ap...@google.com>.
If I recall from the 2.4 discussion, the 2.5 branch should have been cut in
late April. It was cut ~5 weeks late. Keeping to the 6 week release
cadence, we are already late cutting the 2.6 release branch, which should
be cut immediately. Then 2.7 should be cut in mid July.
Andrew
On Mon, Jun 25, 2018 at 12:32 PM Kenneth Knowles <kl...@google.com> wrote:
> Specifically, I mean that since we cut release-2.5.0 branch on Jun 6 we
> would cut release-2.6.0 on July 18.
>
> This time around, we should cut first, cherry-pick second.
>
> Kenn
>
> On Mon, Jun 25, 2018 at 12:21 PM Jean-Baptiste Onofré <jb...@nanthrax.net>
> wrote:
>
>> It makes sense.
>>
>> So, I will start the 2.6.0 process on July 17.
>>
>> Regards
>> JB
>>
>> On 25/06/2018 20:47, Alan Myrvold wrote:
>> > It would be a more predictable cadence to have a consistent timing
>> > between when the release branches are cut, and not when the release is
>> > published.
>> >
>> > If 2.5.0 was cut on June 5, then 2.6.0 could be cut July 17?
>> >
>> > On Mon, Jun 25, 2018 at 10:57 AM Ahmet Altay <altay@google.com
>> > <ma...@google.com>> wrote:
>> >
>> >
>> >
>> > On Mon, Jun 25, 2018 at 10:49 AM, Ahmet Altay <altay@google.com
>> > <ma...@google.com>> wrote:
>> >
>> > JB, thank you for making this release happen.
>> >
>> > I noticed that python artifacts are not deployed to pypi yet.
>> > Would you like me to do that?
>> >
>> > Thank you,
>> > Ahmet
>> >
>> > On Sat, Jun 23, 2018 at 6:45 AM, Rafael Fernandez
>> > <rfernand@google.com <ma...@google.com>> wrote:
>> >
>> > Great news! Thanks so much to our Release Manager and
>> > everybody who helped iron out the wrinkles!
>> >
>> > If you haven't seen it already, look for the thread
>> > "[PROPOSAL] Add a blog post for Beam release 2.5.0
>> > " [1]
>> > in dev@ - Alexey Romanenko has put together a very nice
>> > summary of all the good stuff in 2.5.0.
>> >
>> >
>> > [1]
>> https://lists.apache.org/thread.html/ae3284ca051b800b3edd73ad0f7f62344e26d3957b46794149bf1fb2@%3Cdev.beam.apache.org%3E
>>
>> >
>> > "
>> >
>> > On Fri, Jun 22, 2018 at 8:33 PM Jean-Baptiste Onofré
>> > <jb@nanthrax.net <ma...@nanthrax.net>> wrote:
>> >
>> > I meant August (not July) for next release cycle.
>> >
>> > Regards
>> > JB
>> >
>> > On 23/06/2018 05:17, Jean-Baptiste Onofré wrote:
>> > > Hi all,
>> > >
>> > > I'm happy to announce that we have unanimously
>> > approved this release.
>> > >
>> > > There are 12 approving votes, 5 of which are binding:
>> > > * Ahmet Altay
>> > > * Jean-Baptiste Onofré
>> > > * Lukasz Cwik
>> > > * Reuven Lax
>> > > * Robert Bradshaw
>> > >
>> > > There are no disapproving votes.
>> > >
>> > > I'm finalizing the release.
>> > >
>> > > Thanks everyone!
>> > >
>> > > The 2.6.0 release process is expected to begin in 6
>> > weeks. So we should
>> > > start the Jira triage on Saturday, 4th July and I
>> > would like to start
>> > > the release process on Tuesday 7th.
>> >
>> >
>> > My understanding was that there will be a release every 6 weeks. It
>> > seems like with this plan (to start release process on August 7),
>> > the understanding is that we will have 6 weeks between a release is
>> > out and the start of the next release process. My take is, we need
>> > to have a user centric view and a make promise to release every X
>> > weeks. If X=6 is not sustainable we can discuss. However, having X
>> > weeks in between a release cut and release start will result in
>> > unpredictable release dates.
>> >
>> > What do you think?
>> >
>> >
>> > >
>> > > 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 <http://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 <http://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é
>> > jbonofre@apache.org <ma...@apache.org>
>> > http://blog.nanthrax.net
>> > Talend - http://www.talend.com
>> >
>> >
>> >
>>
>> --
>> Jean-Baptiste Onofré
>> jbonofre@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
>
Re: [RESULT][VOTE] Apache Beam, version 2.5.0, release candidate #2
Posted by Kenneth Knowles <kl...@google.com>.
Specifically, I mean that since we cut release-2.5.0 branch on Jun 6 we
would cut release-2.6.0 on July 18.
This time around, we should cut first, cherry-pick second.
Kenn
On Mon, Jun 25, 2018 at 12:21 PM Jean-Baptiste Onofré <jb...@nanthrax.net>
wrote:
> It makes sense.
>
> So, I will start the 2.6.0 process on July 17.
>
> Regards
> JB
>
> On 25/06/2018 20:47, Alan Myrvold wrote:
> > It would be a more predictable cadence to have a consistent timing
> > between when the release branches are cut, and not when the release is
> > published.
> >
> > If 2.5.0 was cut on June 5, then 2.6.0 could be cut July 17?
> >
> > On Mon, Jun 25, 2018 at 10:57 AM Ahmet Altay <altay@google.com
> > <ma...@google.com>> wrote:
> >
> >
> >
> > On Mon, Jun 25, 2018 at 10:49 AM, Ahmet Altay <altay@google.com
> > <ma...@google.com>> wrote:
> >
> > JB, thank you for making this release happen.
> >
> > I noticed that python artifacts are not deployed to pypi yet.
> > Would you like me to do that?
> >
> > Thank you,
> > Ahmet
> >
> > On Sat, Jun 23, 2018 at 6:45 AM, Rafael Fernandez
> > <rfernand@google.com <ma...@google.com>> wrote:
> >
> > Great news! Thanks so much to our Release Manager and
> > everybody who helped iron out the wrinkles!
> >
> > If you haven't seen it already, look for the thread
> > "[PROPOSAL] Add a blog post for Beam release 2.5.0
> > " [1]
> > in dev@ - Alexey Romanenko has put together a very nice
> > summary of all the good stuff in 2.5.0.
> >
> >
> > [1]
> https://lists.apache.org/thread.html/ae3284ca051b800b3edd73ad0f7f62344e26d3957b46794149bf1fb2@%3Cdev.beam.apache.org%3E
>
> >
> > "
> >
> > On Fri, Jun 22, 2018 at 8:33 PM Jean-Baptiste Onofré
> > <jb@nanthrax.net <ma...@nanthrax.net>> wrote:
> >
> > I meant August (not July) for next release cycle.
> >
> > Regards
> > JB
> >
> > On 23/06/2018 05:17, Jean-Baptiste Onofré wrote:
> > > Hi all,
> > >
> > > I'm happy to announce that we have unanimously
> > approved this release.
> > >
> > > There are 12 approving votes, 5 of which are binding:
> > > * Ahmet Altay
> > > * Jean-Baptiste Onofré
> > > * Lukasz Cwik
> > > * Reuven Lax
> > > * Robert Bradshaw
> > >
> > > There are no disapproving votes.
> > >
> > > I'm finalizing the release.
> > >
> > > Thanks everyone!
> > >
> > > The 2.6.0 release process is expected to begin in 6
> > weeks. So we should
> > > start the Jira triage on Saturday, 4th July and I
> > would like to start
> > > the release process on Tuesday 7th.
> >
> >
> > My understanding was that there will be a release every 6 weeks. It
> > seems like with this plan (to start release process on August 7),
> > the understanding is that we will have 6 weeks between a release is
> > out and the start of the next release process. My take is, we need
> > to have a user centric view and a make promise to release every X
> > weeks. If X=6 is not sustainable we can discuss. However, having X
> > weeks in between a release cut and release start will result in
> > unpredictable release dates.
> >
> > What do you think?
> >
> >
> > >
> > > 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 <http://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 <http://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é
> > jbonofre@apache.org <ma...@apache.org>
> > http://blog.nanthrax.net
> > Talend - http://www.talend.com
> >
> >
> >
>
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
Re: [RESULT][VOTE] Apache Beam, version 2.5.0, release candidate #2
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
It makes sense.
So, I will start the 2.6.0 process on July 17.
Regards
JB
On 25/06/2018 20:47, Alan Myrvold wrote:
> It would be a more predictable cadence to have a consistent timing
> between when the release branches are cut, and not when the release is
> published.
>
> If 2.5.0 was cut on June 5, then 2.6.0 could be cut July 17?
>
> On Mon, Jun 25, 2018 at 10:57 AM Ahmet Altay <altay@google.com
> <ma...@google.com>> wrote:
>
>
>
> On Mon, Jun 25, 2018 at 10:49 AM, Ahmet Altay <altay@google.com
> <ma...@google.com>> wrote:
>
> JB, thank you for making this release happen.
>
> I noticed that python artifacts are not deployed to pypi yet.
> Would you like me to do that?
>
> Thank you,
> Ahmet
>
> On Sat, Jun 23, 2018 at 6:45 AM, Rafael Fernandez
> <rfernand@google.com <ma...@google.com>> wrote:
>
> Great news! Thanks so much to our Release Manager and
> everybody who helped iron out the wrinkles!
>
> If you haven't seen it already, look for the thread
> "[PROPOSAL] Add a blog post for Beam release 2.5.0
> " [1]
> in dev@ - Alexey Romanenko has put together a very nice
> summary of all the good stuff in 2.5.0.
>
>
> [1] https://lists.apache.org/thread.html/ae3284ca051b800b3edd73ad0f7f62344e26d3957b46794149bf1fb2@%3Cdev.beam.apache.org%3E
>
> "
>
> On Fri, Jun 22, 2018 at 8:33 PM Jean-Baptiste Onofré
> <jb@nanthrax.net <ma...@nanthrax.net>> wrote:
>
> I meant August (not July) for next release cycle.
>
> Regards
> JB
>
> On 23/06/2018 05:17, Jean-Baptiste Onofré wrote:
> > Hi all,
> >
> > I'm happy to announce that we have unanimously
> approved this release.
> >
> > There are 12 approving votes, 5 of which are binding:
> > * Ahmet Altay
> > * Jean-Baptiste Onofré
> > * Lukasz Cwik
> > * Reuven Lax
> > * Robert Bradshaw
> >
> > There are no disapproving votes.
> >
> > I'm finalizing the release.
> >
> > Thanks everyone!
> >
> > The 2.6.0 release process is expected to begin in 6
> weeks. So we should
> > start the Jira triage on Saturday, 4th July and I
> would like to start
> > the release process on Tuesday 7th.
>
>
> My understanding was that there will be a release every 6 weeks. It
> seems like with this plan (to start release process on August 7),
> the understanding is that we will have 6 weeks between a release is
> out and the start of the next release process. My take is, we need
> to have a user centric view and a make promise to release every X
> weeks. If X=6 is not sustainable we can discuss. However, having X
> weeks in between a release cut and release start will result in
> unpredictable release dates.
>
> What do you think?
>
>
> >
> > 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 <http://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 <http://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é
> jbonofre@apache.org <ma...@apache.org>
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
>
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: [RESULT][VOTE] Apache Beam, version 2.5.0, release candidate #2
Posted by Kenneth Knowles <kl...@google.com>.
+1 to user-centric view.
Agree with Alan - if we keep a steady cadence with the branch cuts then it
can just be on us to optimize our process for getting it shipped.
I don't think users are too bothered by exact time gap unless it is too
slow, so if this puts some at 4 weeks or even 2 weeks no one will be upset.
It is also nice if there is a comparable amount of change between releases,
another reason to branch every 6 weeks. And finally, if there is a
contributor that is implementing something and wants to get it to users, it
should be able to arrive in <= 6 weeks. That means that if a release sits
on a branch/review for a long time, it should not really slow down other
things done on master in that time.
Kenn
On Mon, Jun 25, 2018 at 11:48 AM Alan Myrvold <am...@google.com> wrote:
> It would be a more predictable cadence to have a consistent timing between
> when the release branches are cut, and not when the release is published.
>
> If 2.5.0 was cut on June 5, then 2.6.0 could be cut July 17?
>
> On Mon, Jun 25, 2018 at 10:57 AM Ahmet Altay <al...@google.com> wrote:
>
>>
>>
>> On Mon, Jun 25, 2018 at 10:49 AM, Ahmet Altay <al...@google.com> wrote:
>>
>>> JB, thank you for making this release happen.
>>>
>>> I noticed that python artifacts are not deployed to pypi yet. Would you
>>> like me to do that?
>>>
>>> Thank you,
>>> Ahmet
>>>
>>> On Sat, Jun 23, 2018 at 6:45 AM, Rafael Fernandez <rf...@google.com>
>>> wrote:
>>>
>>>> Great news! Thanks so much to our Release Manager and everybody who
>>>> helped iron out the wrinkles!
>>>>
>>>> If you haven't seen it already, look for the thread "[PROPOSAL] Add a
>>>> blog post for Beam release 2.5.0
>>>> " [1]
>>>> in dev@ - Alexey Romanenko has put together a very nice summary of
>>>> all the good stuff in 2.5.0.
>>>>
>>>> [1]
>>>> https://lists.apache.org/thread.html/ae3284ca051b800b3edd73ad0f7f62344e26d3957b46794149bf1fb2@%3Cdev.beam.apache.org%3E
>>>>
>>>>
>>>> "
>>>>
>>>> On Fri, Jun 22, 2018 at 8:33 PM Jean-Baptiste Onofré <jb...@nanthrax.net>
>>>> wrote:
>>>>
>>>>> I meant August (not July) for next release cycle.
>>>>>
>>>>> Regards
>>>>> JB
>>>>>
>>>>> On 23/06/2018 05:17, Jean-Baptiste Onofré wrote:
>>>>> > Hi all,
>>>>> >
>>>>> > I'm happy to announce that we have unanimously approved this release.
>>>>> >
>>>>> > There are 12 approving votes, 5 of which are binding:
>>>>> > * Ahmet Altay
>>>>> > * Jean-Baptiste Onofré
>>>>> > * Lukasz Cwik
>>>>> > * Reuven Lax
>>>>> > * Robert Bradshaw
>>>>> >
>>>>> > There are no disapproving votes.
>>>>> >
>>>>> > I'm finalizing the release.
>>>>> >
>>>>> > Thanks everyone!
>>>>> >
>>>>> > The 2.6.0 release process is expected to begin in 6 weeks. So we
>>>>> should
>>>>> > start the Jira triage on Saturday, 4th July and I would like to start
>>>>> > the release process on Tuesday 7th.
>>>>>
>>>>
>> My understanding was that there will be a release every 6 weeks. It seems
>> like with this plan (to start release process on August 7), the
>> understanding is that we will have 6 weeks between a release is out and the
>> start of the next release process. My take is, we need to have a user
>> centric view and a make promise to release every X weeks. If X=6 is not
>> sustainable we can discuss. However, having X weeks in between a release
>> cut and release start will result in unpredictable release dates.
>>
>> What do you think?
>>
>>
>>> >
>>>>> > 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é
>>>>> jbonofre@apache.org
>>>>> http://blog.nanthrax.net
>>>>> Talend - http://www.talend.com
>>>>>
>>>>
>>>
>>
Re: [RESULT][VOTE] Apache Beam, version 2.5.0, release candidate #2
Posted by Alan Myrvold <am...@google.com>.
It would be a more predictable cadence to have a consistent timing between
when the release branches are cut, and not when the release is published.
If 2.5.0 was cut on June 5, then 2.6.0 could be cut July 17?
On Mon, Jun 25, 2018 at 10:57 AM Ahmet Altay <al...@google.com> wrote:
>
>
> On Mon, Jun 25, 2018 at 10:49 AM, Ahmet Altay <al...@google.com> wrote:
>
>> JB, thank you for making this release happen.
>>
>> I noticed that python artifacts are not deployed to pypi yet. Would you
>> like me to do that?
>>
>> Thank you,
>> Ahmet
>>
>> On Sat, Jun 23, 2018 at 6:45 AM, Rafael Fernandez <rf...@google.com>
>> wrote:
>>
>>> Great news! Thanks so much to our Release Manager and everybody who
>>> helped iron out the wrinkles!
>>>
>>> If you haven't seen it already, look for the thread "[PROPOSAL] Add a
>>> blog post for Beam release 2.5.0
>>> " [1]
>>> in dev@ - Alexey Romanenko has put together a very nice summary of all
>>> the good stuff in 2.5.0.
>>>
>>> [1]
>>> https://lists.apache.org/thread.html/ae3284ca051b800b3edd73ad0f7f62344e26d3957b46794149bf1fb2@%3Cdev.beam.apache.org%3E
>>>
>>>
>>> "
>>>
>>> On Fri, Jun 22, 2018 at 8:33 PM Jean-Baptiste Onofré <jb...@nanthrax.net>
>>> wrote:
>>>
>>>> I meant August (not July) for next release cycle.
>>>>
>>>> Regards
>>>> JB
>>>>
>>>> On 23/06/2018 05:17, Jean-Baptiste Onofré wrote:
>>>> > Hi all,
>>>> >
>>>> > I'm happy to announce that we have unanimously approved this release.
>>>> >
>>>> > There are 12 approving votes, 5 of which are binding:
>>>> > * Ahmet Altay
>>>> > * Jean-Baptiste Onofré
>>>> > * Lukasz Cwik
>>>> > * Reuven Lax
>>>> > * Robert Bradshaw
>>>> >
>>>> > There are no disapproving votes.
>>>> >
>>>> > I'm finalizing the release.
>>>> >
>>>> > Thanks everyone!
>>>> >
>>>> > The 2.6.0 release process is expected to begin in 6 weeks. So we
>>>> should
>>>> > start the Jira triage on Saturday, 4th July and I would like to start
>>>> > the release process on Tuesday 7th.
>>>>
>>>
> My understanding was that there will be a release every 6 weeks. It seems
> like with this plan (to start release process on August 7), the
> understanding is that we will have 6 weeks between a release is out and the
> start of the next release process. My take is, we need to have a user
> centric view and a make promise to release every X weeks. If X=6 is not
> sustainable we can discuss. However, having X weeks in between a release
> cut and release start will result in unpredictable release dates.
>
> What do you think?
>
>
>> >
>>>> > 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é
>>>> jbonofre@apache.org
>>>> http://blog.nanthrax.net
>>>> Talend - http://www.talend.com
>>>>
>>>
>>
>
Re: [RESULT][VOTE] Apache Beam, version 2.5.0, release candidate #2
Posted by Ahmet Altay <al...@google.com>.
On Mon, Jun 25, 2018 at 10:49 AM, Ahmet Altay <al...@google.com> wrote:
> JB, thank you for making this release happen.
>
> I noticed that python artifacts are not deployed to pypi yet. Would you
> like me to do that?
>
> Thank you,
> Ahmet
>
> On Sat, Jun 23, 2018 at 6:45 AM, Rafael Fernandez <rf...@google.com>
> wrote:
>
>> Great news! Thanks so much to our Release Manager and everybody who
>> helped iron out the wrinkles!
>>
>> If you haven't seen it already, look for the thread "[PROPOSAL] Add a
>> blog post for Beam release 2.5.0
>> " [1]
>> in dev@ - Alexey Romanenko has put together a very nice summary of all
>> the good stuff in 2.5.0.
>>
>> [1] https://lists.apache.org/thread.html/ae3284ca051b800b3ed
>> d73ad0f7f62344e26d3957b46794149bf1fb2@%3Cdev.beam.apache.org%3E
>>
>> "
>>
>> On Fri, Jun 22, 2018 at 8:33 PM Jean-Baptiste Onofré <jb...@nanthrax.net>
>> wrote:
>>
>>> I meant August (not July) for next release cycle.
>>>
>>> Regards
>>> JB
>>>
>>> On 23/06/2018 05:17, Jean-Baptiste Onofré wrote:
>>> > Hi all,
>>> >
>>> > I'm happy to announce that we have unanimously approved this release.
>>> >
>>> > There are 12 approving votes, 5 of which are binding:
>>> > * Ahmet Altay
>>> > * Jean-Baptiste Onofré
>>> > * Lukasz Cwik
>>> > * Reuven Lax
>>> > * Robert Bradshaw
>>> >
>>> > There are no disapproving votes.
>>> >
>>> > I'm finalizing the release.
>>> >
>>> > Thanks everyone!
>>> >
>>> > The 2.6.0 release process is expected to begin in 6 weeks. So we should
>>> > start the Jira triage on Saturday, 4th July and I would like to start
>>> > the release process on Tuesday 7th.
>>>
>>
My understanding was that there will be a release every 6 weeks. It seems
like with this plan (to start release process on August 7), the
understanding is that we will have 6 weeks between a release is out and the
start of the next release process. My take is, we need to have a user
centric view and a make promise to release every X weeks. If X=6 is not
sustainable we can discuss. However, having X weeks in between a release
cut and release start will result in unpredictable release dates.
What do you think?
> >
>>> > 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é
>>> jbonofre@apache.org
>>> http://blog.nanthrax.net
>>> Talend - http://www.talend.com
>>>
>>
>
Re: [RESULT][VOTE] Apache Beam, version 2.5.0, release candidate #2
Posted by Ahmet Altay <al...@google.com>.
JB, thank you for making this release happen.
I noticed that python artifacts are not deployed to pypi yet. Would you
like me to do that?
Thank you,
Ahmet
On Sat, Jun 23, 2018 at 6:45 AM, Rafael Fernandez <rf...@google.com>
wrote:
> Great news! Thanks so much to our Release Manager and everybody who helped
> iron out the wrinkles!
>
> If you haven't seen it already, look for the thread "[PROPOSAL] Add a blog
> post for Beam release 2.5.0
> " [1]
> in dev@ - Alexey Romanenko has put together a very nice summary of all
> the good stuff in 2.5.0.
>
> [1] https://lists.apache.org/thread.html/ae3284ca051b800b3edd73ad0f7f62
> 344e26d3957b46794149bf1fb2@%3Cdev.beam.apache.org%3E
>
> "
>
> On Fri, Jun 22, 2018 at 8:33 PM Jean-Baptiste Onofré <jb...@nanthrax.net>
> wrote:
>
>> I meant August (not July) for next release cycle.
>>
>> Regards
>> JB
>>
>> On 23/06/2018 05:17, Jean-Baptiste Onofré wrote:
>> > Hi all,
>> >
>> > I'm happy to announce that we have unanimously approved this release.
>> >
>> > There are 12 approving votes, 5 of which are binding:
>> > * Ahmet Altay
>> > * Jean-Baptiste Onofré
>> > * Lukasz Cwik
>> > * Reuven Lax
>> > * Robert Bradshaw
>> >
>> > There are no disapproving votes.
>> >
>> > I'm finalizing the release.
>> >
>> > Thanks everyone!
>> >
>> > The 2.6.0 release process is expected to begin in 6 weeks. So we should
>> > start the Jira triage on Saturday, 4th July and I would like to start
>> > the release process on Tuesday 7th.
>> >
>> > 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é
>> jbonofre@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
>
Re: [RESULT][VOTE] Apache Beam, version 2.5.0, release candidate #2
Posted by Rafael Fernandez <rf...@google.com>.
Great news! Thanks so much to our Release Manager and everybody who helped
iron out the wrinkles!
If you haven't seen it already, look for the thread "[PROPOSAL] Add a blog
post for Beam release 2.5.0
" [1]
in dev@ - Alexey Romanenko has put together a very nice summary of all the
good stuff in 2.5.0.
[1]
https://lists.apache.org/thread.html/ae3284ca051b800b3edd73ad0f7f62344e26d3957b46794149bf1fb2@%3Cdev.beam.apache.org%3E
"
On Fri, Jun 22, 2018 at 8:33 PM Jean-Baptiste Onofré <jb...@nanthrax.net>
wrote:
> I meant August (not July) for next release cycle.
>
> Regards
> JB
>
> On 23/06/2018 05:17, Jean-Baptiste Onofré wrote:
> > Hi all,
> >
> > I'm happy to announce that we have unanimously approved this release.
> >
> > There are 12 approving votes, 5 of which are binding:
> > * Ahmet Altay
> > * Jean-Baptiste Onofré
> > * Lukasz Cwik
> > * Reuven Lax
> > * Robert Bradshaw
> >
> > There are no disapproving votes.
> >
> > I'm finalizing the release.
> >
> > Thanks everyone!
> >
> > The 2.6.0 release process is expected to begin in 6 weeks. So we should
> > start the Jira triage on Saturday, 4th July and I would like to start
> > the release process on Tuesday 7th.
> >
> > 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é
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
Re: [RESULT][VOTE] Apache Beam, version 2.5.0, release candidate #2
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
I meant August (not July) for next release cycle.
Regards
JB
On 23/06/2018 05:17, Jean-Baptiste Onofré wrote:
> Hi all,
>
> I'm happy to announce that we have unanimously approved this release.
>
> There are 12 approving votes, 5 of which are binding:
> * Ahmet Altay
> * Jean-Baptiste Onofré
> * Lukasz Cwik
> * Reuven Lax
> * Robert Bradshaw
>
> There are no disapproving votes.
>
> I'm finalizing the release.
>
> Thanks everyone!
>
> The 2.6.0 release process is expected to begin in 6 weeks. So we should
> start the Jira triage on Saturday, 4th July and I would like to start
> the release process on Tuesday 7th.
>
> 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é
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
[RESULT][VOTE] Apache Beam, version 2.5.0, release candidate #2
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi all,
I'm happy to announce that we have unanimously approved this release.
There are 12 approving votes, 5 of which are binding:
* Ahmet Altay
* Jean-Baptiste Onofré
* Lukasz Cwik
* Reuven Lax
* Robert Bradshaw
There are no disapproving votes.
I'm finalizing the release.
Thanks everyone!
The 2.6.0 release process is expected to begin in 6 weeks. So we should
start the Jira triage on Saturday, 4th July and I would like to start
the release process on Tuesday 7th.
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é
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: [VOTE] Apache Beam, version 2.5.0, release candidate #2
Posted by Boyuan Zhang <bo...@google.com>.
Hey JB,
Could you please share your apache-beam-wheels repo and your build log?
Maybe we can help debug together.
Boyuan
On Fri, Jun 22, 2018 at 7:51 AM Jean-Baptiste Onofré <jb...@nanthrax.net>
wrote:
> Gently reminder for the PMC member.
>
> Right now, if I'm not wrong, we only have two concrete binding votes
> (Luke and I).
>
> As reminder, to pass, the vote needs at least 3 binding votes (a binding
> vote is a vote from a PMC member).
>
> So, we would need an additional formal binding vote.
>
> NB: I prepared the apache-beam-wheels on my github and trigger a build
> on Travis. However, I have a build issue that I have to investigate.
>
> Thanks,
> 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é
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
Re: [VOTE] Apache Beam, version 2.5.0, release candidate #2
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Thanks Robert,
I'm closing the vote.
Regards
JB
On 22/06/2018 20:48, Robert Bradshaw wrote:
> I was waiting for the gradlew jar file to be removed from the source
> release, but I figured it made more sense to just jump in and help
> out.
>
> $ git show-ref github/release-2.5.0
> 093ac64bc2d59f3d58c0f0e7f65f2a36eaf26a4a refs/remotes/github/release-2.5.0
>
> $ wget https://github.com/apache/beam/archive/release-2.5.0.zip -O
> apache-beam-2.5.0-source-release.zip
> $ zip -d apache-beam-2.5.0-source-release.zip
> beam-release-2.5.0/gradle/wrapper/gradle-wrapper.jar
> [signed and uploaded]
>
> I also uploaded the wheels to dist (which I worked on with Boyuan, and
> were verified by Yifan), putting all the python artifacts in a python
> sub-directory.
>
> I can now say +1 (binding) to this release.
> On Fri, Jun 22, 2018 at 9:47 AM Ahmet Altay <al...@google.com> wrote:
>>
>> I already voted a +1 2 days ago.
>>
>> Again:
>>
>> +1 (binding)
>>
>> Thank you JB!
>>
>> On Fri, Jun 22, 2018 at 9:23 AM, Alan Myrvold <am...@google.com> wrote:
>>>
>>> The https://dist.apache.org/repos/dist/dev/beam/2.5.0/apache-beam-2.5.0-source-release.zip still contains the beam-release-2.5.0/gradle/wrapper/gradle-wrapper.jar. Does that need to be removed before releasing it?
>>>
>>> On Fri, Jun 22, 2018 at 9:11 AM Reuven Lax <re...@google.com> wrote:
>>>>
>>>> +1 (binding)
>>>>
>>>> On Fri, Jun 22, 2018 at 7:51 AM Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
>>>>>
>>>>> Gently reminder for the PMC member.
>>>>>
>>>>> Right now, if I'm not wrong, we only have two concrete binding votes
>>>>> (Luke and I).
>>>>>
>>>>> As reminder, to pass, the vote needs at least 3 binding votes (a binding
>>>>> vote is a vote from a PMC member).
>>>>>
>>>>> So, we would need an additional formal binding vote.
>>>>>
>>>>> NB: I prepared the apache-beam-wheels on my github and trigger a build
>>>>> on Travis. However, I have a build issue that I have to investigate.
>>>>>
>>>>> Thanks,
>>>>> 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é
>>>>> jbonofre@apache.org
>>>>> http://blog.nanthrax.net
>>>>> Talend - http://www.talend.com
>>
>>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: [VOTE] Apache Beam, version 2.5.0, release candidate #2
Posted by Alan Myrvold <am...@google.com>.
+1
Thanks for removing the jar, Robert.
On Fri, Jun 22, 2018 at 11:48 AM Robert Bradshaw <ro...@google.com>
wrote:
> I was waiting for the gradlew jar file to be removed from the source
> release, but I figured it made more sense to just jump in and help
> out.
>
> $ git show-ref github/release-2.5.0
> 093ac64bc2d59f3d58c0f0e7f65f2a36eaf26a4a refs/remotes/github/release-2.5.0
>
> $ wget https://github.com/apache/beam/archive/release-2.5.0.zip -O
> apache-beam-2.5.0-source-release.zip
> $ zip -d apache-beam-2.5.0-source-release.zip
> beam-release-2.5.0/gradle/wrapper/gradle-wrapper.jar
> [signed and uploaded]
>
> I also uploaded the wheels to dist (which I worked on with Boyuan, and
> were verified by Yifan), putting all the python artifacts in a python
> sub-directory.
>
> I can now say +1 (binding) to this release.
> On Fri, Jun 22, 2018 at 9:47 AM Ahmet Altay <al...@google.com> wrote:
> >
> > I already voted a +1 2 days ago.
> >
> > Again:
> >
> > +1 (binding)
> >
> > Thank you JB!
> >
> > On Fri, Jun 22, 2018 at 9:23 AM, Alan Myrvold <am...@google.com>
> wrote:
> >>
> >> The
> https://dist.apache.org/repos/dist/dev/beam/2.5.0/apache-beam-2.5.0-source-release.zip
> still contains the beam-release-2.5.0/gradle/wrapper/gradle-wrapper.jar.
> Does that need to be removed before releasing it?
> >>
> >> On Fri, Jun 22, 2018 at 9:11 AM Reuven Lax <re...@google.com> wrote:
> >>>
> >>> +1 (binding)
> >>>
> >>> On Fri, Jun 22, 2018 at 7:51 AM Jean-Baptiste Onofré <jb...@nanthrax.net>
> wrote:
> >>>>
> >>>> Gently reminder for the PMC member.
> >>>>
> >>>> Right now, if I'm not wrong, we only have two concrete binding votes
> >>>> (Luke and I).
> >>>>
> >>>> As reminder, to pass, the vote needs at least 3 binding votes (a
> binding
> >>>> vote is a vote from a PMC member).
> >>>>
> >>>> So, we would need an additional formal binding vote.
> >>>>
> >>>> NB: I prepared the apache-beam-wheels on my github and trigger a build
> >>>> on Travis. However, I have a build issue that I have to investigate.
> >>>>
> >>>> Thanks,
> >>>> 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é
> >>>> jbonofre@apache.org
> >>>> http://blog.nanthrax.net
> >>>> Talend - http://www.talend.com
> >
> >
>
Re: [VOTE] Apache Beam, version 2.5.0, release candidate #2
Posted by Robert Bradshaw <ro...@google.com>.
I was waiting for the gradlew jar file to be removed from the source
release, but I figured it made more sense to just jump in and help
out.
$ git show-ref github/release-2.5.0
093ac64bc2d59f3d58c0f0e7f65f2a36eaf26a4a refs/remotes/github/release-2.5.0
$ wget https://github.com/apache/beam/archive/release-2.5.0.zip -O
apache-beam-2.5.0-source-release.zip
$ zip -d apache-beam-2.5.0-source-release.zip
beam-release-2.5.0/gradle/wrapper/gradle-wrapper.jar
[signed and uploaded]
I also uploaded the wheels to dist (which I worked on with Boyuan, and
were verified by Yifan), putting all the python artifacts in a python
sub-directory.
I can now say +1 (binding) to this release.
On Fri, Jun 22, 2018 at 9:47 AM Ahmet Altay <al...@google.com> wrote:
>
> I already voted a +1 2 days ago.
>
> Again:
>
> +1 (binding)
>
> Thank you JB!
>
> On Fri, Jun 22, 2018 at 9:23 AM, Alan Myrvold <am...@google.com> wrote:
>>
>> The https://dist.apache.org/repos/dist/dev/beam/2.5.0/apache-beam-2.5.0-source-release.zip still contains the beam-release-2.5.0/gradle/wrapper/gradle-wrapper.jar. Does that need to be removed before releasing it?
>>
>> On Fri, Jun 22, 2018 at 9:11 AM Reuven Lax <re...@google.com> wrote:
>>>
>>> +1 (binding)
>>>
>>> On Fri, Jun 22, 2018 at 7:51 AM Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
>>>>
>>>> Gently reminder for the PMC member.
>>>>
>>>> Right now, if I'm not wrong, we only have two concrete binding votes
>>>> (Luke and I).
>>>>
>>>> As reminder, to pass, the vote needs at least 3 binding votes (a binding
>>>> vote is a vote from a PMC member).
>>>>
>>>> So, we would need an additional formal binding vote.
>>>>
>>>> NB: I prepared the apache-beam-wheels on my github and trigger a build
>>>> on Travis. However, I have a build issue that I have to investigate.
>>>>
>>>> Thanks,
>>>> 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é
>>>> jbonofre@apache.org
>>>> http://blog.nanthrax.net
>>>> Talend - http://www.talend.com
>
>
Re: [VOTE] Apache Beam, version 2.5.0, release candidate #2
Posted by Ahmet Altay <al...@google.com>.
I already voted a +1 2 days ago.
Again:
+1 (binding)
Thank you JB!
On Fri, Jun 22, 2018 at 9:23 AM, Alan Myrvold <am...@google.com> wrote:
> The https://dist.apache.org/repos/dist/dev/beam/2.5.0/
> apache-beam-2.5.0-source-release.zip still contains
> the beam-release-2.5.0/gradle/wrapper/gradle-wrapper.jar. Does that need
> to be removed before releasing it?
>
> On Fri, Jun 22, 2018 at 9:11 AM Reuven Lax <re...@google.com> wrote:
>
>> +1 (binding)
>>
>> On Fri, Jun 22, 2018 at 7:51 AM Jean-Baptiste Onofré <jb...@nanthrax.net>
>> wrote:
>>
>>> Gently reminder for the PMC member.
>>>
>>> Right now, if I'm not wrong, we only have two concrete binding votes
>>> (Luke and I).
>>>
>>> As reminder, to pass, the vote needs at least 3 binding votes (a binding
>>> vote is a vote from a PMC member).
>>>
>>> So, we would need an additional formal binding vote.
>>>
>>> NB: I prepared the apache-beam-wheels on my github and trigger a build
>>> on Travis. However, I have a build issue that I have to investigate.
>>>
>>> Thanks,
>>> 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é
>>> jbonofre@apache.org
>>> http://blog.nanthrax.net
>>> Talend - http://www.talend.com
>>>
>>
Re: [VOTE] Apache Beam, version 2.5.0, release candidate #2
Posted by Alan Myrvold <am...@google.com>.
The
https://dist.apache.org/repos/dist/dev/beam/2.5.0/apache-beam-2.5.0-source-release.zip
still contains the beam-release-2.5.0/gradle/wrapper/gradle-wrapper.jar.
Does that need to be removed before releasing it?
On Fri, Jun 22, 2018 at 9:11 AM Reuven Lax <re...@google.com> wrote:
> +1 (binding)
>
> On Fri, Jun 22, 2018 at 7:51 AM Jean-Baptiste Onofré <jb...@nanthrax.net>
> wrote:
>
>> Gently reminder for the PMC member.
>>
>> Right now, if I'm not wrong, we only have two concrete binding votes
>> (Luke and I).
>>
>> As reminder, to pass, the vote needs at least 3 binding votes (a binding
>> vote is a vote from a PMC member).
>>
>> So, we would need an additional formal binding vote.
>>
>> NB: I prepared the apache-beam-wheels on my github and trigger a build
>> on Travis. However, I have a build issue that I have to investigate.
>>
>> Thanks,
>> 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é
>> jbonofre@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
>
Re: [VOTE] Apache Beam, version 2.5.0, release candidate #2
Posted by Reuven Lax <re...@google.com>.
+1 (binding)
On Fri, Jun 22, 2018 at 7:51 AM Jean-Baptiste Onofré <jb...@nanthrax.net>
wrote:
> Gently reminder for the PMC member.
>
> Right now, if I'm not wrong, we only have two concrete binding votes
> (Luke and I).
>
> As reminder, to pass, the vote needs at least 3 binding votes (a binding
> vote is a vote from a PMC member).
>
> So, we would need an additional formal binding vote.
>
> NB: I prepared the apache-beam-wheels on my github and trigger a build
> on Travis. However, I have a build issue that I have to investigate.
>
> Thanks,
> 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é
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
Re: [VOTE] Apache Beam, version 2.5.0, release candidate #2
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Gently reminder for the PMC member.
Right now, if I'm not wrong, we only have two concrete binding votes
(Luke and I).
As reminder, to pass, the vote needs at least 3 binding votes (a binding
vote is a vote from a PMC member).
So, we would need an additional formal binding vote.
NB: I prepared the apache-beam-wheels on my github and trigger a build
on Travis. However, I have a build issue that I have to investigate.
Thanks,
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é
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com