On Tue, Feb 20, 2018 at 3:46 PM, Bakul Shah <ba...@bitblocks.com> wrote:
> May be one can write a tool around or similar to "vgo test" to > test and update not to the latest but some earlier version. > For example, if pkg A currently imports C v1.x and B imports C > v1.y, through iterative testing one may find C v1.z that works > for both and update go.mod files for both A & B. > > The underlying concern is that with better tooling to manage > versioning, there will also be more versions to manage as > there is less of an incentive to try to make things work with > the latest versions of imported packages. I wondered if there > is a way to encourage/improve the quality/correctness aspect. > One vague idea is to consider specifying tests (in go.mod) to > be run prior to an update. Sort of like asserts in code. > In the tour (research.swtch.com/vgo-tour) I show how "all" is redefined to be useful again. So it's completely reasonable to try an update, go test all, and if all the tests pass (and you trust your tests), then check in the go.mod file. Someone could build a bot to do this automatically, even. I don't think minimal version selection means you're always stuck with old versions. It just means you don't get new versions until you ask for them and are ready to evaluate how good they are, not just because you run 'go get' and a new version has appeared overnight. Thanks. Russ -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
