Re: Hello Beam Community!!!

[Griselda Cuevas]

Welcome!

On Fri, Aug 3, 2018, 9:44 PM Jean-Baptiste Onofré  wrote:

> Welcome aboard !
>
> Regards
> JB
>
> On 04/08/2018 04:39, Connell O'Callaghan wrote:
> > Hi All
> >
> > My name is Connell. I am relatively new to Beam (and Google where I work
> > as a technical PM). My philosophy is very much oriented around how can I
> > serve the team. Hence, I am extremely interested to learn how I can help
> > continue the great work of this community. One particular area I am
> > curious about is how this community triages and manages issues. I will
> > do some self study on this. But I would be very interested to engage
> > with others interested in this general topic. Please let me know if you
> > wish to connect on this or other topics!!!
> >
> > Thank you in advance!!!
> >
> > - Connell
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: Hello Beam Community!!!

[Jean-Baptiste Onofré]

Welcome aboard !

Regards
JB

On 04/08/2018 04:39, Connell O'Callaghan wrote:
> Hi All 
> 
> My name is Connell. I am relatively new to Beam (and Google where I work
> as a technical PM). My philosophy is very much oriented around how can I
> serve the team. Hence, I am extremely interested to learn how I can help
> continue the great work of this community. One particular area I am
> curious about is how this community triages and manages issues. I will
> do some self study on this. But I would be very interested to engage
> with others interested in this general topic. Please let me know if you
> wish to connect on this or other topics!!! 
> 
> Thank you in advance!!! 
> 
> - Connell 

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

Re: Hello Beam Community!!!

[Ahmet Altay]

Welcome! Looking forward to your contributions.

On Fri, Aug 3, 2018 at 7:39 PM, Connell O'Callaghan 
wrote:

> Hi All
>
> My name is Connell. I am relatively new to Beam (and Google where I work
> as a technical PM). My philosophy is very much oriented around how can I
> serve the team. Hence, I am extremely interested to learn how I can help
> continue the great work of this community. One particular area I am curious
> about is how this community triages and manages issues. I will do some self
> study on this. But I would be very interested to engage with others
> interested in this general topic. Please let me know if you wish to connect
> on this or other topics!!!
>
> Thank you in advance!!!
>
> - Connell
>

Hello Beam Community!!!

[Connell O'Callaghan]

Hi All

My name is Connell. I am relatively new to Beam (and Google where I work as
a technical PM). My philosophy is very much oriented around how can I serve
the team. Hence, I am extremely interested to learn how I can help continue
the great work of this community. One particular area I am curious about is
how this community triages and manages issues. I will do some self study on
this. But I would be very interested to engage with others interested in
this general topic. Please let me know if you wish to connect on this or
other topics!!!

Thank you in advance!!!

- Connell

[VOTE] Apache Beam, version 2.6.0, release candidate #2

[Pablo Estrada]

Hello everyone!

Extra, extra! The Apache Beam 2.6.0 release candidate #2 is out.

Please review and vote on the release candidate #2 for the version 2.6.0,
as follows:

[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)

The complete staged set of artifacts 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
2F1FEDCDF6DD7990422F482F65224E0292DD8A51 [3],
* all artifacts to be deployed to the Maven Central Repository [4],
* source code tag "v2.6.0-RC2" [5],
* website pull request listing the release and publishing the API reference
manual [6]. This did not change from the previous RC.
* 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.

Regards
-Pablo.

[1]
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527&version=12343392
[2] https://dist.apache.org/repos/dist/dev/beam/2.6.0/
[3] https://dist.apache.org/repos/dist/dev/beam/KEYS
[4] https://repository.apache.org/content/repositories/orgapachebeam-1045/
[5] https://github.com/apache/beam/tree/v2.6.0-RC2
[6] https://github.com/apache/beam-site/pull/518
-- 
Got feedback? go/pabloem-feedback

Re: [VOTE] Apache Beam, version 2.6.0, release candidate #1

[Pablo Estrada]

Hello all,
as per Valentyn's feedback, RC1 has blocking issues, so I will move ahead
to build RC2.
Best
-P.

On Fri, Aug 3, 2018 at 11:15 AM Valentyn Tymofieiev 
wrote:

> -1.
> Unfortunately we discovered an issue that can cause pipelines to crash
> when Cythonized version of the SDK is used:
> https://issues.apache.org/jira/browse/BEAM-5069
> I think we will need another RC that has the fix. Note that we can
> continue validating RC1 - if there are any issues remaining, it's better if
> we can discover them in RC1 that in RC2.
>
> Thanks,
> Valentyn
>
> On Fri, Aug 3, 2018 at 1:19 AM Tim Robertson 
> wrote:
>
>> +1 (non binding)
>>
>> With apologies to Valentyn and others, but only had time to test what was
>> feasible for us this week. Tested our existing pipelines using 2.6.0RC1
>> which source and sink using AvroIO / HDFS on Spark 2.3 (Cloudera) ran
>> without issue - our project tests all pass with 2.6.0RC1.
>>
>> We'd like to raise that BEAM-4750 is noticeable and our project builds
>> have slowed significantly (tests). In general we encourage effort
>> towards (and thank those progressing) structured monitoring of
>> performance across releases.
>>
>>
>>
>> On Fri, Aug 3, 2018 at 9:32 AM, Valentyn Tymofieiev 
>> wrote:
>>
>>> Just wanted to highlight again to folks who are interested to help with
>>> qualifying the release: release validation checklist
>>> 
>>>   has
>>> 2.6.0 tab that shows what has been tested so far for this RC.
>>>
>>> Please sign up and add your results. It may be helpful to include in the
>>> spreadsheet which operation system was used to test the SDK.
>>>
>>> Some helpful links:
>>>
>>> https://beam.apache.org/contribute/release-guide/#run-validation-tests
>>> - these are instructions how to perform release validation steps.
>>> https://beam.apache.org/get-started/ - these are instructions Beam
>>> users may actually be following when trying out Beam.
>>> https://s.apache.org/beam-release-validation - Validation
>>> checklist/acceptance criteria.
>>>
>>> Also it looks like these links may need to be updated to better reflect
>>> required action items to cover SQL and Go SDK.
>>>
>>> thanks,
>>> Valentyn
>>>
>>>
>>> On Thu, Aug 2, 2018 at 10:07 PM Suneel Marthi 
>>> wrote:
>>>
 +1 non-binding

 1. tested with beam samples
 2. verified sigs and hashes of artifacts


 On Fri, Aug 3, 2018 at 12:43 AM, Jean-Baptiste Onofré 
 wrote:

> +1 (binding)
>
> Tested with beam-samples.
>
> I didn't have time to include three Jira, but 2.7.0 should be in vote
> in
> soon ;)
>
> Regards
> JB
>
> On 01/08/2018 01:50, Pablo Estrada wrote:
> > Hello everyone!
> >
> > I have been able to prepare a release candidate for Beam 2.6.0. : D
> >
> > Please review and vote on the release candidate #1 for the version
> > 2.6.0, as follows:
> >
> > [ ] +1, Approve the release
> > [ ] -1, Do not approve the release (please provide specific comments)
> >
> > The complete staged set of artifacts 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 2F1FEDCDF6DD7990422F482F65224E0292DD8A51 [3],
> > * all artifacts to be deployed to the Maven Central Repository [4],
> > * source code tag "v2.6.0-RC1" [5],
> > * website pull request listing the release and publishing the API
> > reference manual [6].
> > * 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.
> >
> > Regards
> > -Pablo.
> >
> > [1]
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527&version=12343392
> > [2] https://dist.apache.org/repos/dist/dev/beam/2.6.0/
> > [3] https://dist.apache.org/repos/dist/dev/beam/KEYS
> > [4]
> https://repository.apache.org/content/repositories/orgapachebeam-1044/
> > [5] https://github.com/apache/beam/tree/v2.6.0-RC1
> > [6] https://github.com/apache/beam-site/pull/518
> >
> > --
> > Got feedback? go/pabloem-feedback
> 
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>


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

Re: Community Examples Repository

[Charles Chen]

We should separate out the decision for (1) whether examples should be
packaged separately upon release and (2) where the example will live
code-wise, i.e. whether we want another repo.  With respect to the first
item, I think the proposal needs more detail before we can decide here--for
example, if we separate out the packaging for the examples, we need to
change our build process and potentially release additional PyPI packages
and this should be thought about before we can make a decision.

On Fri, Aug 3, 2018 at 3:23 PM Pablo Estrada  wrote:

> Hello all,
> I see a number of mixed responses. I think it would be helpful to push for
> a decision by calling for a vote.
>
> Also, the proposal has a number of parts, so perhaps we could ask David
> and other contributors of the proposal to outline a couple alternatives the
> we can all vote on. (e.g. #1 no examples repo, #2 all examples to new repo,
> #3 examples repo, but some examples remain in main repo).
>
> The outcome may be no change at all, or some change, but at least we'll
> have a definite decision from the community.
>
> Does that sound reasonable?
> -P.
>
> On Thu, Aug 2, 2018 at 11:09 AM Ankur Goenka  wrote:
>
>> I like he initiative but I feel that fragmenting the codebase will make
>> it harder to discover examples. Having examples in a separate repo makes it
>> easier to forget that examples should get the same love as the rest of the
>> codebase.
>> The other challenge is the tooling and integration which is harder with
>> multiple repo.
>> It makes sense to isolate the examples and make them more obvious.
>> A sub project of examples as mentioned in the discussion might be
>> sufficient without having much overhead.
>>
>> Thanks,
>> Ankur
>>
>>
>> On Thu, Aug 2, 2018 at 10:52 AM Kai Jiang  wrote:
>>
>>> Agreed with Rui. We could also add more SQL examples (like, different
>>> IOs ) for everyone to get started with.
>>>
>>> Best,
>>> Kai
>>>
>>> On 2018/08/02 17:40:32, Rui Wang  wrote:
>>> > I might miss it: are examples to be moved including those which are not
>>> > under example/? For example there are some BeamSQL examples in
>>> > org/apache/beam/sdk/extensions/sql/example
>>> > <
>>> https://github.com/apache/beam/tree/master/sdks/java/extensions/sql/src/main/java/org/apache/beam/sdk/extensions/sql/example
>>> >
>>> > .
>>> >
>>> >
>>> > It's better to keep BeamSQL examples in where it is because related API
>>> > might still change.
>>> >
>>> > -Rui
>>> >
>>> > On Thu, Aug 2, 2018 at 8:58 AM Ahmet Altay  wrote:
>>> >
>>> > > Robert, I agree with you in general. However there is also a second
>>> > > motivation. There is an increase in new PRs that are coming to add
>>> new
>>> > > examples. This is great however the core code (including
>>> distributions) is
>>> > > not a great place to host such examples. An examples repo would help
>>> in
>>> > > this case. It could also serve as an entry point for new
>>> contributors.
>>> > >
>>> > >
>>> > >
>>> > > On Thu, Aug 2, 2018 at 12:40 AM, Robert Bradshaw <
>>> rober...@google.com>
>>> > > wrote:
>>> > >
>>> > >> I have to admit I'm generally -1 on moving examples to a separate
>>> > >> repository. In particular, I think it would actually inhibit the
>>> > >> stated goals of increasing visibility and better keeping them up to
>>> > >> date, and for all the reasons we just migrated the beam-site
>>> directory
>>> > >> in. It seems the primary motivation is that it's difficult in Java
>>> to
>>> > >> have a portion of the repo that depends on another as if it were
>>> > >> "external" (i.e. the way others would use Beam) rather than being a
>>> > >> sub-project of Beam. Is this not doable?
>>> > >> On Wed, Aug 1, 2018 at 10:59 PM Charles Chen 
>>> wrote:
>>> > >> >
>>> > >> > I would also prefer that examples be linked to releases so that
>>> we can
>>> > >> build and test them during development; i.e. if your commit breaks
>>> > >> wordcount, we want to know right away so we can revert.  Perhaps we
>>> can
>>> > >> keep these in the repo but more clearly modularize the artifacts we
>>> release?
>>> > >> >
>>> > >> > For the Python SDK, if we separate this out in any way, there is
>>> the
>>> > >> separate issue of dealing with namespace packages (which are kind
>>> of broken
>>> > >> and poorly supported:
>>> > >> https://github.com/pypa/python-packaging-user-guide/issues/265),
>>> if we
>>> > >> want to keep the examples under the apache_beam.examples module
>>> path.  See
>>> > >> also
>>> https://packaging.python.org/guides/packaging-namespace-packages/.
>>> > >> >
>>> > >> > On Wed, Aug 1, 2018 at 9:29 PM j...@nanthrax.net 
>>> wrote:
>>> > >> >>
>>> > >> >> Hi,
>>> > >> >>
>>> > >> >> I don't have problem to move the examples in a dedicated
>>> repository.
>>> > >> However, IMHO, we have to:
>>> > >> >>
>>> > >> >> 1. Keep a build of examples linked to latest core
>>> release/SNAPSHOT
>>> > >> >> 2. Include the examples in the distribution (convenient for the
>>> users)
>>> > >> >>
>>

Re: Apache Beam Python Wheels Repository

[Ahmet Altay]

This LGTM, also greatly simplifies the creation of wheel files for multiple
platforms.

I can file an INFRA ticket to create a new repo to host wheel setup. Does
anybody have experience with setting up a new repo similar to this?

Ahmet

On Fri, Aug 3, 2018 at 1:16 PM, Boyuan Zhang  wrote:

> Hey all,
>
> I'm Boyuan Zhang from Google Dataflow Team, currently helping Release
> Manager(Pablo Estrada) with 2.6.0 release. Since Beam decided to release
> python wheels since 2.5.0, we need to create a wrapper repository(sample
> repo ) under apache to
> build and stage released python wheels for each release. Anyone can help to
> create this repository?
>
> Thanks for all your help! Happy Friday~
>
> Boyuan Zhang
>

Re: Community Examples Repository

[Pablo Estrada]

Hello all,
I see a number of mixed responses. I think it would be helpful to push for
a decision by calling for a vote.

Also, the proposal has a number of parts, so perhaps we could ask David and
other contributors of the proposal to outline a couple alternatives the we
can all vote on. (e.g. #1 no examples repo, #2 all examples to new repo, #3
examples repo, but some examples remain in main repo).

The outcome may be no change at all, or some change, but at least we'll
have a definite decision from the community.

Does that sound reasonable?
-P.

On Thu, Aug 2, 2018 at 11:09 AM Ankur Goenka  wrote:

> I like he initiative but I feel that fragmenting the codebase will make it
> harder to discover examples. Having examples in a separate repo makes it
> easier to forget that examples should get the same love as the rest of the
> codebase.
> The other challenge is the tooling and integration which is harder with
> multiple repo.
> It makes sense to isolate the examples and make them more obvious.
> A sub project of examples as mentioned in the discussion might be
> sufficient without having much overhead.
>
> Thanks,
> Ankur
>
>
> On Thu, Aug 2, 2018 at 10:52 AM Kai Jiang  wrote:
>
>> Agreed with Rui. We could also add more SQL examples (like, different IOs
>> ) for everyone to get started with.
>>
>> Best,
>> Kai
>>
>> On 2018/08/02 17:40:32, Rui Wang  wrote:
>> > I might miss it: are examples to be moved including those which are not
>> > under example/? For example there are some BeamSQL examples in
>> > org/apache/beam/sdk/extensions/sql/example
>> > <
>> https://github.com/apache/beam/tree/master/sdks/java/extensions/sql/src/main/java/org/apache/beam/sdk/extensions/sql/example
>> >
>> > .
>> >
>> >
>> > It's better to keep BeamSQL examples in where it is because related API
>> > might still change.
>> >
>> > -Rui
>> >
>> > On Thu, Aug 2, 2018 at 8:58 AM Ahmet Altay  wrote:
>> >
>> > > Robert, I agree with you in general. However there is also a second
>> > > motivation. There is an increase in new PRs that are coming to add new
>> > > examples. This is great however the core code (including
>> distributions) is
>> > > not a great place to host such examples. An examples repo would help
>> in
>> > > this case. It could also serve as an entry point for new contributors.
>> > >
>> > >
>> > >
>> > > On Thu, Aug 2, 2018 at 12:40 AM, Robert Bradshaw > >
>> > > wrote:
>> > >
>> > >> I have to admit I'm generally -1 on moving examples to a separate
>> > >> repository. In particular, I think it would actually inhibit the
>> > >> stated goals of increasing visibility and better keeping them up to
>> > >> date, and for all the reasons we just migrated the beam-site
>> directory
>> > >> in. It seems the primary motivation is that it's difficult in Java to
>> > >> have a portion of the repo that depends on another as if it were
>> > >> "external" (i.e. the way others would use Beam) rather than being a
>> > >> sub-project of Beam. Is this not doable?
>> > >> On Wed, Aug 1, 2018 at 10:59 PM Charles Chen  wrote:
>> > >> >
>> > >> > I would also prefer that examples be linked to releases so that we
>> can
>> > >> build and test them during development; i.e. if your commit breaks
>> > >> wordcount, we want to know right away so we can revert.  Perhaps we
>> can
>> > >> keep these in the repo but more clearly modularize the artifacts we
>> release?
>> > >> >
>> > >> > For the Python SDK, if we separate this out in any way, there is
>> the
>> > >> separate issue of dealing with namespace packages (which are kind of
>> broken
>> > >> and poorly supported:
>> > >> https://github.com/pypa/python-packaging-user-guide/issues/265), if
>> we
>> > >> want to keep the examples under the apache_beam.examples module
>> path.  See
>> > >> also
>> https://packaging.python.org/guides/packaging-namespace-packages/.
>> > >> >
>> > >> > On Wed, Aug 1, 2018 at 9:29 PM j...@nanthrax.net 
>> wrote:
>> > >> >>
>> > >> >> Hi,
>> > >> >>
>> > >> >> I don't have problem to move the examples in a dedicated
>> repository.
>> > >> However, IMHO, we have to:
>> > >> >>
>> > >> >> 1. Keep a build of examples linked to latest core release/SNAPSHOT
>> > >> >> 2. Include the examples in the distribution (convenient for the
>> users)
>> > >> >>
>> > >> >> On another topic, I think it would be better to avoid usage of
>> Google
>> > >> Doc for such kind of discussion and directly share on the mailing
>> list (at
>> > >> least a summary/light details).
>> > >> >>
>> > >> >> Regards
>> > >> >> JB
>> > >> >>
>> > >> >> On Thursday, August 02, 2018 00:12 CEST, David Cavazos <
>> > >> dcava...@google.com> wrote:
>> > >> >>
>> > >> >>
>> > >> >> Hi everyone!
>> > >> >>
>> > >> >> We wanted to migrate the examples from the core repository to a
>> new
>> > >> Beam community examples repository. As the number of examples grow,
>> it
>> > >> makes sense to modularize and decouple the core functionality from
>> the
>> > >> examples.
>> > >> >>
>> > >> >> We will als

Apache Beam Python Wheels Repository

[Boyuan Zhang]

Hey all,

I'm Boyuan Zhang from Google Dataflow Team, currently helping Release
Manager(Pablo Estrada) with 2.6.0 release. Since Beam decided to release
python wheels since 2.5.0, we need to create a wrapper repository(sample
repo ) under apache to
build and stage released python wheels for each release. Anyone can help to
create this repository?

Thanks for all your help! Happy Friday~

Boyuan Zhang

Re: [VOTE] Apache Beam, version 2.6.0, release candidate #1

[Valentyn Tymofieiev]

-1.
Unfortunately we discovered an issue that can cause pipelines to crash when
Cythonized version of the SDK is used:
https://issues.apache.org/jira/browse/BEAM-5069
I think we will need another RC that has the fix. Note that we can continue
validating RC1 - if there are any issues remaining, it's better if we can
discover them in RC1 that in RC2.

Thanks,
Valentyn

On Fri, Aug 3, 2018 at 1:19 AM Tim Robertson 
wrote:

> +1 (non binding)
>
> With apologies to Valentyn and others, but only had time to test what was
> feasible for us this week. Tested our existing pipelines using 2.6.0RC1
> which source and sink using AvroIO / HDFS on Spark 2.3 (Cloudera) ran
> without issue - our project tests all pass with 2.6.0RC1.
>
> We'd like to raise that BEAM-4750 is noticeable and our project builds
> have slowed significantly (tests). In general we encourage effort towards
> (and thank those progressing) structured monitoring of performance across
> releases.
>
>
>
> On Fri, Aug 3, 2018 at 9:32 AM, Valentyn Tymofieiev 
> wrote:
>
>> Just wanted to highlight again to folks who are interested to help with
>> qualifying the release: release validation checklist
>> 
>>   has
>> 2.6.0 tab that shows what has been tested so far for this RC.
>>
>> Please sign up and add your results. It may be helpful to include in the
>> spreadsheet which operation system was used to test the SDK.
>>
>> Some helpful links:
>>
>> https://beam.apache.org/contribute/release-guide/#run-validation-tests
>> - these are instructions how to perform release validation steps.
>> https://beam.apache.org/get-started/ - these are instructions Beam users
>> may actually be following when trying out Beam.
>> https://s.apache.org/beam-release-validation - Validation
>> checklist/acceptance criteria.
>>
>> Also it looks like these links may need to be updated to better reflect
>> required action items to cover SQL and Go SDK.
>>
>> thanks,
>> Valentyn
>>
>>
>> On Thu, Aug 2, 2018 at 10:07 PM Suneel Marthi  wrote:
>>
>>> +1 non-binding
>>>
>>> 1. tested with beam samples
>>> 2. verified sigs and hashes of artifacts
>>>
>>>
>>> On Fri, Aug 3, 2018 at 12:43 AM, Jean-Baptiste Onofré 
>>> wrote:
>>>
 +1 (binding)

 Tested with beam-samples.

 I didn't have time to include three Jira, but 2.7.0 should be in vote in
 soon ;)

 Regards
 JB

 On 01/08/2018 01:50, Pablo Estrada wrote:
 > Hello everyone!
 >
 > I have been able to prepare a release candidate for Beam 2.6.0. : D
 >
 > Please review and vote on the release candidate #1 for the version
 > 2.6.0, as follows:
 >
 > [ ] +1, Approve the release
 > [ ] -1, Do not approve the release (please provide specific comments)
 >
 > The complete staged set of artifacts 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 2F1FEDCDF6DD7990422F482F65224E0292DD8A51 [3],
 > * all artifacts to be deployed to the Maven Central Repository [4],
 > * source code tag "v2.6.0-RC1" [5],
 > * website pull request listing the release and publishing the API
 > reference manual [6].
 > * 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.
 >
 > Regards
 > -Pablo.
 >
 > [1]
 >
 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527&version=12343392
 > [2] https://dist.apache.org/repos/dist/dev/beam/2.6.0/
 > [3] https://dist.apache.org/repos/dist/dev/beam/KEYS
 > [4]
 https://repository.apache.org/content/repositories/orgapachebeam-1044/
 > [5] https://github.com/apache/beam/tree/v2.6.0-RC1
 > [6] https://github.com/apache/beam-site/pull/518
 >
 > --
 > Got feedback? go/pabloem-feedback
 

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

>>>
>>>
>

Re: [VOTE] Apache Beam, version 2.6.0, release candidate #1

[Tim Robertson]

+1 (non binding)

With apologies to Valentyn and others, but only had time to test what was
feasible for us this week. Tested our existing pipelines using 2.6.0RC1
which source and sink using AvroIO / HDFS on Spark 2.3 (Cloudera) ran
without issue - our project tests all pass with 2.6.0RC1.

We'd like to raise that BEAM-4750 is noticeable and our project builds have
slowed significantly (tests). In general we encourage effort towards (and
thank those progressing) structured monitoring of performance across
releases.



On Fri, Aug 3, 2018 at 9:32 AM, Valentyn Tymofieiev 
wrote:

> Just wanted to highlight again to folks who are interested to help with
> qualifying the release: release validation checklist
> 
>   has
> 2.6.0 tab that shows what has been tested so far for this RC.
>
> Please sign up and add your results. It may be helpful to include in the
> spreadsheet which operation system was used to test the SDK.
>
> Some helpful links:
>
> https://beam.apache.org/contribute/release-guide/#run-validation-tests  -
> these are instructions how to perform release validation steps.
> https://beam.apache.org/get-started/ - these are instructions Beam users
> may actually be following when trying out Beam.
> https://s.apache.org/beam-release-validation - Validation
> checklist/acceptance criteria.
>
> Also it looks like these links may need to be updated to better reflect
> required action items to cover SQL and Go SDK.
>
> thanks,
> Valentyn
>
>
> On Thu, Aug 2, 2018 at 10:07 PM Suneel Marthi  wrote:
>
>> +1 non-binding
>>
>> 1. tested with beam samples
>> 2. verified sigs and hashes of artifacts
>>
>>
>> On Fri, Aug 3, 2018 at 12:43 AM, Jean-Baptiste Onofré 
>> wrote:
>>
>>> +1 (binding)
>>>
>>> Tested with beam-samples.
>>>
>>> I didn't have time to include three Jira, but 2.7.0 should be in vote in
>>> soon ;)
>>>
>>> Regards
>>> JB
>>>
>>> On 01/08/2018 01:50, Pablo Estrada wrote:
>>> > Hello everyone!
>>> >
>>> > I have been able to prepare a release candidate for Beam 2.6.0. : D
>>> >
>>> > Please review and vote on the release candidate #1 for the version
>>> > 2.6.0, as follows:
>>> >
>>> > [ ] +1, Approve the release
>>> > [ ] -1, Do not approve the release (please provide specific comments)
>>> >
>>> > The complete staged set of artifacts 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 2F1FEDCDF6DD7990422F482F65224E0292DD8A51 [3],
>>> > * all artifacts to be deployed to the Maven Central Repository [4],
>>> > * source code tag "v2.6.0-RC1" [5],
>>> > * website pull request listing the release and publishing the API
>>> > reference manual [6].
>>> > * 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.
>>> >
>>> > Regards
>>> > -Pablo.
>>> >
>>> > [1]
>>> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
>>> projectId=12319527&version=12343392
>>> > [2] https://dist.apache.org/repos/dist/dev/beam/2.6.0/
>>> > [3] https://dist.apache.org/repos/dist/dev/beam/KEYS
>>> > [4] https://repository.apache.org/content/repositories/
>>> orgapachebeam-1044/
>>> > [5] https://github.com/apache/beam/tree/v2.6.0-RC1
>>> > [6] https://github.com/apache/beam-site/pull/518
>>> >
>>> > --
>>> > Got feedback? go/pabloem-feedback
>>> 
>>>
>>> --
>>> Jean-Baptiste Onofré
>>> jbono...@apache.org
>>> http://blog.nanthrax.net
>>> Talend - http://www.talend.com
>>>
>>
>>

Re: [VOTE] Apache Beam, version 2.6.0, release candidate #1

[Valentyn Tymofieiev]

Just wanted to highlight again to folks who are interested to help with
qualifying the release: release validation checklist

 has
2.6.0 tab that shows what has been tested so far for this RC.

Please sign up and add your results. It may be helpful to include in the
spreadsheet which operation system was used to test the SDK.

Some helpful links:

https://beam.apache.org/contribute/release-guide/#run-validation-tests  -
these are instructions how to perform release validation steps.
https://beam.apache.org/get-started/ - these are instructions Beam users
may actually be following when trying out Beam.
https://s.apache.org/beam-release-validation - Validation
checklist/acceptance criteria.

Also it looks like these links may need to be updated to better reflect
required action items to cover SQL and Go SDK.

thanks,
Valentyn


On Thu, Aug 2, 2018 at 10:07 PM Suneel Marthi  wrote:

> +1 non-binding
>
> 1. tested with beam samples
> 2. verified sigs and hashes of artifacts
>
>
> On Fri, Aug 3, 2018 at 12:43 AM, Jean-Baptiste Onofré 
> wrote:
>
>> +1 (binding)
>>
>> Tested with beam-samples.
>>
>> I didn't have time to include three Jira, but 2.7.0 should be in vote in
>> soon ;)
>>
>> Regards
>> JB
>>
>> On 01/08/2018 01:50, Pablo Estrada wrote:
>> > Hello everyone!
>> >
>> > I have been able to prepare a release candidate for Beam 2.6.0. : D
>> >
>> > Please review and vote on the release candidate #1 for the version
>> > 2.6.0, as follows:
>> >
>> > [ ] +1, Approve the release
>> > [ ] -1, Do not approve the release (please provide specific comments)
>> >
>> > The complete staged set of artifacts 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 2F1FEDCDF6DD7990422F482F65224E0292DD8A51 [3],
>> > * all artifacts to be deployed to the Maven Central Repository [4],
>> > * source code tag "v2.6.0-RC1" [5],
>> > * website pull request listing the release and publishing the API
>> > reference manual [6].
>> > * 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.
>> >
>> > Regards
>> > -Pablo.
>> >
>> > [1]
>> >
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527&version=12343392
>> > [2] https://dist.apache.org/repos/dist/dev/beam/2.6.0/
>> > [3] https://dist.apache.org/repos/dist/dev/beam/KEYS
>> > [4]
>> https://repository.apache.org/content/repositories/orgapachebeam-1044/
>> > [5] https://github.com/apache/beam/tree/v2.6.0-RC1
>> > [6] https://github.com/apache/beam-site/pull/518
>> >
>> > --
>> > Got feedback? go/pabloem-feedback
>> 
>>
>> --
>> Jean-Baptiste Onofré
>> jbono...@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
>
>