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.

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

May 9th, 2022 Community Meeting #84

Closed
qu1queee opened this issue May 4, 2022 · 5 comments
Closed

May 9th, 2022 Community Meeting #84

qu1queee opened this issue May 4, 2022 · 5 comments

Comments

@qu1queee
Copy link
Contributor

qu1queee commented May 4, 2022

  • Please add a topic in this thread and add a link to the GitHub issue associated with the topic.
  • Please make sure you give folks enough time to review/discuss the topic offline on GitHub before coming into the meeting
  • (optional) Paste the image of an animal 😸
@qu1queee
Copy link
Contributor Author

qu1queee commented May 4, 2022

@SaschaSchwarze0
Copy link
Member

Should we move to Go 1.18 ?

🐑

@SaschaSchwarze0
Copy link
Member

SaschaSchwarze0 commented May 9, 2022

go-containerregistry contains a Container Registry implementation. This is useful in unit tests.

🐣

@SaschaSchwarze0
Copy link
Member

Somebody interested to review SHIP-0033: Image vulnerability scanning #81 ?

🐇

@SaschaSchwarze0
Copy link
Member

SaschaSchwarze0 commented May 9, 2022

How to release bug fixes:

  • today, we don't create branches for releases (or major-minor versions)
  • we will need a defined process for this
  • Corey: we should branch when we cut a minor release (something like release-0.9)
  • Matthias: cherry-pick commits into that branch
  • Tags would then be v0.9.1 created from release release-0.9
    -> should document this procedure somewhere in the community repository (as a ship)
  • Matthias: do we need an SLA how long we support a release
    • Otavio: only latest release during alpha
    • Otavio: for GA we would need a different story
    • Sascha: for Beta, we should at least have a public statement
    • For the time being, whenever we release something, we should mention that this is an Alpha-project in the release notes
  • Issue: Add SHIP about creating a fix release #85

Go 1.18

Documentation from MD to AsciiDoc (https://asciidoc.org/)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants