Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Go 1.15 released #50

Closed
atc0005 opened this issue Aug 11, 2020 · 3 comments
Closed

Go 1.15 released #50

atc0005 opened this issue Aug 11, 2020 · 3 comments
Assignees
@atc0005
Labels
dependencies oldstable stable unstable
Milestone
v0.2.4

Comments

@atc0005
Copy link
Owner

atc0005 commented Aug 11, 2020

Need to refresh oldstable to use Go 1.14 and stable to use the new Go 1.15 version.

References to Go 1.13 can be removed entirely.

The Go 1.15rc2-based unstable container ... I'm not sure. It may have to stay as-is until the next official RC is available? Another approach would be to push new, lightly tested (or even entirely untested) changes out via this container.
@atc0005 atc0005 self-assigned this Aug 11, 2020
This was referenced Aug 12, 2020
Merged
Closed
Merged
atc0005 added a commit that referenced this issue Aug 12, 2020
@atc0005
Update "oldstable" details
f78025f 
- Switch from Go 1.13.x to 1.14.x series
- Attempt to exclude Go 1.15.x updates for this image

refs GH-50
@atc0005 atc0005 mentioned this issue Aug 12, 2020
Merged
@atc0005
Copy link
Owner Author

atc0005 commented Aug 12, 2020

The Go 1.15rc2-based unstable container ... I'm not sure. It may have to stay as-is until the next official RC is available? Another approach would be to push new, lightly tested (or even entirely untested) changes out via this container.

I'm thinking that would be the way to go here.

I can update the Dockerfile to:

  • allow installation of the latest changes from the master branch for both staticcheck and golangci-lint
  • use the stable series of Go container base images until the next alpha/beta/rc release is available, then switch out the base image to that

@atc0005 atc0005 pinned this issue Aug 12, 2020
@atc0005 atc0005 added this to the Next Release milestone Aug 22, 2020
@atc0005
Copy link
Owner Author

atc0005 commented Aug 27, 2020 •
edited

The Go 1.15rc2-based unstable container ... I'm not sure. It may have to stay as-is until the next official RC is available?

Per https://golang.org/s/release, https://github.com/golang/go/wiki/Go-Release-Cycle:

  • Betas are planned for May/June and November/December
  • RC1 in December/January and June/July
  • Final in February and August

It's probably worth using beta/rc versions for the "unstable" variant when they're available, then switching to the latest stable when they're no longer needed.

@atc0005 atc0005 mentioned this issue Sep 2, 2020
Closed
atc0005 added a commit that referenced this issue Sep 2, 2020
@atc0005
Update README to mention unstable img linters
b347e12 
Note that the `unstable` variant will be used to test new
linters prior to inclusion in the other variants.

refs GH-64, GH-50
@atc0005 atc0005 mentioned this issue Sep 2, 2020
Merged
atc0005 added a commit that referenced this issue Sep 2, 2020
@atc0005
Fix unstable img lint cfg file copy steps
ea92535 
I evidently wasn't paying close enough attention when
multi-tasking earlier.

refs GH-64, GH-50
@atc0005 atc0005 mentioned this issue Sep 2, 2020
Merged
@atc0005
Copy link
Owner Author

atc0005 commented Sep 2, 2020

Considering this resolved per linked PRs.

@atc0005 atc0005 closed this as completed Sep 2, 2020
@atc0005 atc0005 unpinned this issue Sep 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@atc0005 atc0005

Labels
dependencies oldstable stable unstable
Projects
None yet
Milestone
v0.2.4
Development

No branches or pull requests
1 participant
@atc0005