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

April 8th, 2024 Community Meeting #199

Closed
SaschaSchwarze0 opened this issue Apr 2, 2024 · 3 comments
Closed

April 8th, 2024 Community Meeting #199

SaschaSchwarze0 opened this issue Apr 2, 2024 · 3 comments

Comments

@SaschaSchwarze0
Copy link
Member

  • 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 😸
@SaschaSchwarze0
Copy link
Member Author

For PRs related to patch-releases, do we want to create a GitHub milestone, so that we can associate it ?

@adambkaplan
Copy link
Member

Notes from TAG App-Delivery meeting

@qu1queee
Copy link
Contributor

qu1queee commented Apr 8, 2024

Meeting minutes:

  • We usually mark a PR with a release label, which belongs to a milestone. Do we need a milestone for patch releases?
    • Yes, we agreed on following this approach. Upon a fix, we will need to define the milestone, without a due date. @SaschaSchwarze0 to create a v0.12.x milestone, as there is an upcoming patch release for v0.12.0
  • On TAG App-Delivery meeting notes
    • Our ROADMAP is missing clear statements on how to collaborate with CNCF projects we rely on.
  • On v0.13.0 release, to ship Build, CLI this week. Operator is blocked at the moment. Blog post is blocked as well.

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

No branches or pull requests

3 participants