As someone who works on an active runner that's not in the core codebase (the IBM Streams one), we'd like to stay in the matrix and if that means requiring a link to an external page that's easy enough to provide.
Thanks,
John
----- Original message -----
From: Robert Bradshaw <[email protected]>
To: [email protected]
Cc:
Subject: Re: Compatibility Matrix vs Runners in the code base
Date: Fri, Sep 21, 2018 5:07 AM
I don't know that we need to limit the matrix to runners in the Beam codebase (in fact, I could envision a world where most runners live in an upstream codebase), but at the very lease each of these runners should have a link to a page about using that runner with Beam.On Fri, Sep 21, 2018 at 10:57 AM Maximilian Michels <[email protected]> wrote:Hi Beamers,
There have been occasions where people asked me about Runner XY and I
had to find out that it only exists in the compatibility matrix, but not
as part of our code base. More interestingly, I couldn't even find its
code or documentation via my favorite search engine.
This seems to be the case for multiple Runners in the matrix.
The compatibility matrix will need an overhaul anyways with the
portability changes, but what do you think about limiting the matrix to
Runners in the Beam code base?
Thanks,
Max
