Thanks Kenn and Aljoscha! I've added a bunch of issues and reorganized some
of existing ones as per the proposal. Of course, anyone should feel free to
make changes if something is off or doesn't make sense.
I would like to call out a few of the new issues:
* BEAM-2899: "Universal Local Runner
+1
Sounds great!
> On 9. Sep 2017, at 00:44, Kenneth Knowles wrote:
>
> +1 to this.
>
> It is really easy to lose track of things in a sea of tickets, and
> portability touches every SDK and runner, so getting this organized will be
> hugely helpful. Especially getting some clear higher-level
+1 to this.
It is really easy to lose track of things in a sea of tickets, and
portability touches every SDK and runner, so getting this organized will be
hugely helpful. Especially getting some clear higher-level milestones (by
moving tickets to subtasks) we can work towards and announce when don
Hi everyone,
The portability effort involves a large amount of work cutting across all
SDKs and runners [e..g, 1,2,3,4]. It seems to be only partially captured in
JIRAs, so I'd like to volunteer to try to flesh it out further. In addition
to adding JIRAs for missing work, I was thinking of organi
