I'm reading "The next time..." as the Go developers needs to take some
special precautions the next time they merge from master to go-sdk? If
that's correct, that's more than reasonable, especially in light of this
Please do whatever's necessary to make things right again. If there's some
inconvenience for Go, we can certainly manage it.
On Tue, Mar 6, 2018 at 2:42 PM, Kenneth Knowles <k...@google.com> wrote:
> Hi all,
> You may have noticed that our tests are red. A pull request that was meant
> for the Go SDK branch accidentally got merged onto the master branch.
> Things have been merged to master since then.
> I've opened a revert at https://github.com/apache/beam/pull/4808
> The next time there is a master to go-sdk merge it will need to be
> Two other options are (1) leave it there and disable it in whatever way
> and (2) rebase dropping the commit and force push master (breaks all
> checkouts that are past it).