Major Description
Related to eventing:
The primary motivation was that they needed to update gocb - the version in trinity.xml is 2.2.5 which is EOL. However, newer versions required updating to gocbcore v10, and that introduces a cascade of new dependencies - more than we're willing to fork and add to the trinity.xml manifest going forward. It seems likely that goxdcr will have the same issue, correct? If so, it may finally be time to switch the goxdcr build to using proper Go modules as well. I don't think it will be a particularly hard transition for goxdcr.
GoXDCR can look into go modules in a future release