Go Version Policy

[vcabbage]

I was hacking on ToDD today and ended up using a Go 1.7 feature. I reverted the change, but I was wondering if you have any thoughts on which versions current development on ToDD should support.

For reference, the Go team only supports the current version (they might release critical security fixes for n-1). Release Policy

As ToDD is an app and not a library, there's little reason to maintain backwards compatibility. I would suggest supporting the latest released version of Go.

[bigmstone]

This also highlights the need for getting another release under ToDD's belt and getting some packaging in place. @Mierdin and I have spoken about this outside of github, but probably time to spin a version. Finishing Alpha release milestone and wrapping up #26 should be top of mind. (My .02)

In general I agree with keeping it w/ the latest go version. Someone would have to convince me why not doing this would be a good idea, and even then I could only believe it's in certain circumstances.

[Mierdin]

Yes, I agree that the latest version of Go should be used until something solid prevents such a policy.

I also agree with having an alpha release and easy installation and packaging. When I have a chance to work on ToDD that's been my biggest priority.

Closing this as I think we have consensus on this issue 😄