Re: Gradle Status [April 6]

So if I understand correctly, we've migrated all precommit, most postcommits, and we have a working release process using Gradle. There are a few bugs left, but at this pace it sounds like we're close to fully migrated. I know that multiple people put it long hours last getting this done last

Re: About the Gauge metric API

Interesting point. Some runners might implement metrics via a control plane, in which case per-key stuff is problematic for large numbers of keys. However other runners may decide to implement metrics inside the graph itself (e.g. by generating a CombinePerKey), in which case per-key aggregation

Re: About the Gauge metric API

Great summary overall. A few small things to add, along with a note that more examples of the intended is for each metric/aggregation may be helpful. It is worth looking at what existing metric systems provide. Specifically, two things to consider: 1. Is scoping implict / automatic or explicit.

Build failed in Jenkins: beam_Release_NightlySnapshot #738

See Changes: [wcn] Add float support for the SDK. [herohde] [BEAM-3250] Migrate Dataflow ValidatesRunner test to Gradle [herohde] CR: use 4 forks in Dataflow test [herohde] [BEAM-3250] Migrate