I think this would be very useful! Finding breaking changes early is always better than waiting until it's too late.
Reuven On Thu, Dec 7, 2017 at 8:00 PM, Holden Karau <[email protected]> wrote: > Also, and I know this is maybe a bit beyond the scope of what would make > sense initially, but if you wanted to set up something to test BEAM against > the new Spark/Flink RCs we could give feedback about any breaking changes > we see in upstream projects and I’d be happy to help with that :) > > On Fri, Dec 8, 2017 at 9:44 AM Eugene Kirpichov <[email protected]> > wrote: > >> Awesome, excited to see release validation automated! Please let me know >> if you need help getting Flink and Spark runner validation on Dataproc - I >> did that manually and it involved some non-obvious steps. >> >> On Thu, Dec 7, 2017 at 5:29 PM Alan Myrvold <[email protected]> wrote: >> >>> Hi, I'm Alan. >>> >>> I've been working with Google Cloud engineering productivity, and I'm >>> keen on improving the Beam release process and build/test infrastructure. >>> >>> I will be first looking into scripting some of the release validation >>> steps for the nightly java snapshot releases, but hope to learn and improve >>> the whole development and testing experience for Beam. >>> >>> Look forward to working with everyone! >>> >>> Alan Myrvold >>> >>> -- > Twitter: https://twitter.com/holdenkarau >
