Re: Beam 2.4.0

The features/bugfixes included in a release are determined by the time between cutting release branches. So I'd focus on that cadence (outside of special requests). Kenn On Thu, Mar 1, 2018 at 12:33 PM, Robert Bradshaw wrote: > On Thu, Mar 1, 2018 at 9:17 AM Ismaël Mejía

Re: Instructions to install Python SDK from source

There used to be a README when the Python SDK was not yet in master. I worked on it as my first contribution to Beam. This is what it looked like the last time I touched it: *https://github.com/apache/beam/pull/1726/files#diff-4fdc1cf711ab8b1a145ac7ebbe76d937

Re: Beam 2.4.0

On Thu, Mar 1, 2018 at 9:17 AM Ismaël Mejía wrote: > The average time just in the vote process for Beam since we are out of the > incubator is 17.5 days with an average of 75 days between versions. > Good thought to look at history. I think there's general consensus that this

Re: Beam 2.4.0

The average time just in the vote process for Beam since we are out of the incubator is 17.5 days with an average of 75 days between versions. Version Vote Period No. days 2.3.030/01-16/02 17 days (83 days since last) 2.2.027/10-25/11 29 days (101 days since last) 2.1.0

Merging Python code? Help avoid Python 3 regressions with these two simple steps :)

I may have watched too many buzzfeed videos this week but the steps are: 1) git checkout the PR in question 2) Run tox -e lint_py2,lint_py3 This is important since Python 3 isn't installed on the Jenkins workers just yet and we have some tests to catch basic invalid Python 3 which we can slowly

Re: Merging Python code? Help avoid Python 3 regressions with these two simple steps :)

I think we should prioritize the issue of installing Python 3 on the workers (https://issues.apache.org/jira/browse/BEAM-3671). I would appreciate if folks pay attention to these 2 steps but I am worried that it will be easily forgotten. On Thu, Mar 1, 2018 at 6:51 PM, Holden Karau