Re: Proper developer instructions for Python SDK

On Mon, May 22, 2017 at 11:13 AM, Chamikara Jayalath wrote: > (moving to a separate thread) > > On Mon, May 22, 2017 at 10:45 AM Robert Bradshaw > wrote: > >> On Sun, May 21, 2017 at 11:45 AM, Dan Halperin >> wrote:

Proper developer instructions for Python SDK

(moving to a separate thread) On Mon, May 22, 2017 at 10:45 AM Robert Bradshaw wrote: > On Sun, May 21, 2017 at 11:45 AM, Dan Halperin > wrote: > > I think this is an unrealistic request -- Python and Java workflows are > > completely

Re: Behavior of Top.Largest

On Mon, May 22, 2017 at 10:47 AM, Robert Bradshaw < rober...@google.com.invalid> wrote: > > For a simple rename like this, I would at least strongly encourage > fixing both for those that are capable. > Agreed. My response suffered from premature generalization, wandering off into "policy"-esque

Re: Behavior of Top.Largest

On Mon, May 22, 2017 at 10:24 AM, Kenneth Knowles wrote: > There was a brief discussion on a JIRA about following the pattern like: > > Main task: API change proposal > - subtask: Java change > - subtask: Python change > - subtask: ... etc ... We should at least do

Re: Beam 2.0 Release Q and A

Gentle reminder to fill out the Q and A https://docs.google.com/document/d/1vyel3XRfdeGyqLvXiy1C3mrw9QBbveoKjjVLuRxMw4k/edit#. As James said, this is very helpful to new Beam users. On Thu, May 18, 2017 at 3:12 AM James wrote: > Thanks a lot Jesse! Learned a lot from your

Re: New doc: Beam Runner Guide

Cool, I’ll give this a read once I’m back from conference season. :-) > On 22. May 2017, at 07:12, Kenneth Knowles wrote: > > Hi all, > > I spent a little time since 2.0.0 to write a guide for runner authors, > aimed at covering everything you need to know and what you need to

Jenkins build is back to normal : beam_Release_NightlySnapshot #423

See