Git Product home page Git Product logo

Comments (3)

roberthorn avatar roberthorn commented on May 27, 2024

Given the sad state of package management in Go, I guess strict versioning doesn't really matter? Especially in the pre-1.0 stages. But having a semantic versioning scheme may be useful if some package management tool gets accepted in the future.

Dave Cheney gives his opinion on versioning here: https://dave.cheney.net/2016/06/24/gophers-please-tag-your-releases

Maybe there's a better way to automate the documentation and such?

from godoctor.

rdallman avatar rdallman commented on May 27, 2024

Perhaps we should remove any references to the version on the docs and/or web site and those are always assumed to be latest (if web and git are in docs then it should be easy enough to track updates)? It may also be entirely possible to use the /releases/latest link and parse that, which seems not working properly for us as all our releases seem to be 'pre-releases' and for some reason aren't fully qualified enough to be latest. wat. Using commit sha would create the same issue where every commit would have to update the docs, no?

I've a release script laying around for doing some of this stuff like bumping and tagging versions, we may be able to extend it easily enough to any further uses. I will make a note to fiddle with it and make a release branch we can just use with CI to do releases for us.

I think there's some value in having separate versions from whatever is tip on master as it at least gives the illusion that we have done extensive testing on a commit that also has a tag and we think it's okay to use (no intermediary commits or regressions known, etc).. For us, over time it seems like it will mostly be saying that x version is updated to support version 1.x of Go (types package and such) and it's useful to be able to have that broken out in releases if for some reason people are e.g. stuck on go 1.4 they can keep using an older version (bad example, 1.4 may already be broke over vendoring but idk :)

from godoctor.

joverbey avatar joverbey commented on May 27, 2024

Thanks for the comments. I agree it makes sense to stick with tagged versions.

It's really not difficult to tag and update. Not sure why I was whining about that. I added instructions to godoctor/INTERNALS and www/README to make it easier next time (won't forget steps).

from godoctor.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.