4 ms·

Maybe they can use https://NewReleases.io https://NewReleases.io to track Go releases.

entity345 8y ago
Golang has an announcements mail list. I'm sure than projects that depend on the language already subscribe to it. Surely.
- pythonist 8y ago
  But sometimes golang docker images are late for a few days which is very annoying if your ci build pipeline depend on them. It would be great if Go team would be able to update docker images as well. And I am sure that this automation would not be so hard to do.
  - entity345 8y ago
    What requirement do you have to update Go's version on the very day it is released? If you rely on such docker image then upgrade only after it is released.
    - masklinn 8y ago
      > What requirement do you have to update Go's version on the very day it is released? The ability to test / CI that your library works properly?
      - entity345 8y ago
        No, that does not require upgrading to the latest version on the day it is released.
        masklinn 8y ago
        Yeah it does. You'll have downstream users on it as soon as it gets released.
      - elithrar 8y ago
        If it’s a critical part of your infra, building your own container images isn’t a huge ask. Use gimme[0] to install your preferred version of Go into the container. [0]: https://github.com/travis-ci/gimme https://github.com/travis-ci/gimme
      - PopsiclePete 8y ago
        That’s what Go’s bets and rc builds are specifically for - to test your code against a new version before it’s available. The only changes to Go during an rc are ceirical bug fixes.
    - pythonist 8y ago
      For some organizations unpredictable docker image releases are considered unreliable to use at all. Sometimes the image is updated the same day, sometimes after a few days, earlier even after more than a week. The gap between developer tools and infrastructure support for them should be as small as possible this days. It's 2019.
      - entity345 8y ago
        My question is: Why do you need to upgrade your developer tools immediately?
        pythonist 8y ago
        I think that the question is, why wouldn't you? There are already a lot of work and testing done on projects that depend on 1.12 features, but using beta and rc releases. Final 1.12 version would just confirm that everything works, but without docker image, testing on staging infrastructure is delayed even the final version is out. This is why I have https://NewReleases.io https://NewReleases.io configured to track both Go GitHub releases as well as golang image tags on Docker Hub.
        entity345 8y ago
        > I think that the question is, why wouldn't you? We already have a reply to that in your case with the availability of the docker image. In general, people do not rush into upgrading to a new release of any software because it's risky. > There are already a lot of work and testing done on projects that depend on 1.12 features The only reason I can think of is that you have a requirement to support TLS 1.3. And there is no 'delay', as, surely, you plan based on the availability of everything you need (or build your own container image).
        pythonist 8y ago
        So you do not need it as you do not want to use it too soon. That is cool. Others may need docker image release aligned with regular release, and I think that there is nothing wrong with that. Especially for the people that are trying to contribute to Go by testing beta and rc releases.

Golang has an announcements mail list. I'm sure than projects that depend on the language already subscribe to it. Surely.

pythonist 8y ago
But sometimes golang docker images are late for a few days which is very annoying if your ci build pipeline depend on them. It would be great if Go team would be able to update docker images as well. And I am sure that this automation would not be so hard to do.
- entity345 8y ago
  What requirement do you have to update Go's version on the very day it is released? If you rely on such docker image then upgrade only after it is released.
  - masklinn 8y ago
    > What requirement do you have to update Go's version on the very day it is released? The ability to test / CI that your library works properly?
    - entity345 8y ago
      No, that does not require upgrading to the latest version on the day it is released.
      - masklinn 8y ago
        Yeah it does. You'll have downstream users on it as soon as it gets released.
    - elithrar 8y ago
      If it’s a critical part of your infra, building your own container images isn’t a huge ask. Use gimme[0] to install your preferred version of Go into the container. [0]: https://github.com/travis-ci/gimme https://github.com/travis-ci/gimme
    - PopsiclePete 8y ago
      That’s what Go’s bets and rc builds are specifically for - to test your code against a new version before it’s available. The only changes to Go during an rc are ceirical bug fixes.
  - pythonist 8y ago
    For some organizations unpredictable docker image releases are considered unreliable to use at all. Sometimes the image is updated the same day, sometimes after a few days, earlier even after more than a week. The gap between developer tools and infrastructure support for them should be as small as possible this days. It's 2019.
    - entity345 8y ago
      My question is: Why do you need to upgrade your developer tools immediately?
      - pythonist 8y ago
        I think that the question is, why wouldn't you? There are already a lot of work and testing done on projects that depend on 1.12 features, but using beta and rc releases. Final 1.12 version would just confirm that everything works, but without docker image, testing on staging infrastructure is delayed even the final version is out. This is why I have https://NewReleases.io https://NewReleases.io configured to track both Go GitHub releases as well as golang image tags on Docker Hub.
        entity345 8y ago
        > I think that the question is, why wouldn't you? We already have a reply to that in your case with the availability of the docker image. In general, people do not rush into upgrading to a new release of any software because it's risky. > There are already a lot of work and testing done on projects that depend on 1.12 features The only reason I can think of is that you have a requirement to support TLS 1.3. And there is no 'delay', as, surely, you plan based on the availability of everything you need (or build your own container image).
        pythonist 8y ago
        So you do not need it as you do not want to use it too soon. That is cool. Others may need docker image release aligned with regular release, and I think that there is nothing wrong with that. Especially for the people that are trying to contribute to Go by testing beta and rc releases.