On Wed, Sep 20, 2017 at 8:42 PM, Kenneth Knowles <k...@google.com.invalid> wrote: > +1 to a point release to unbreak users. I'm agnostic as to whether to do so > by pinning one thing or unpinning another. Different philosophies there.
The safe immediate change is to restrict to the formerly known good version. Given that apitools has fixed this upstream, we may float all dependencies up long term. > On Tue, Sep 19, 2017 at 9:35 PM, Jean-Baptiste Onofré <j...@nanthrax.net> > wrote: > >> +1 >> >> Regards >> JB >> >> On 09/19/2017 11:05 PM, Charles Chen wrote: >> >>> The latest version (2.1.0) of Beam Python ( >>> https://pypi.python.org/pypi/apache-beam) is broken due to a change in >>> the >>> "six" dependency (BEAM-2964 >>> <https://issues.apache.org/jira/browse/BEAM-2964>). For instance, >>> installing "apache-beam" in a clean environment and running "python -m >>> apache_beam.examples.wordcount" results in a failure. This issue is >>> fixed >>> at head with Robert's recent PR (https://github.com/apache/beam/pull/3865 >>> ). >>> >>> I propose to cherry-pick this change on top of the 2.1.0 release branch >>> (to >>> form a new 2.1.1 release branch) and call a vote to release version 2.1.1 >>> only for Beam Python. >>> >>> Alternatively, to preserve version alignment we could also re-release Beam >>> Java 2.1.1 with the same code as 2.1.0 modulo the version bump. Thoughts? >>> >>> Best, >>> Charles >>> >>> >> -- >> Jean-Baptiste Onofré >> jbono...@apache.org >> http://blog.nanthrax.net >> Talend - http://www.talend.com >>
