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 12th, 2021 Community Meeting #701

Closed
qu1queee opened this issue Mar 30, 2021 · 9 comments
Closed

April 12th, 2021 Community Meeting #701

qu1queee opened this issue Mar 30, 2021 · 9 comments

Comments

@qu1queee
Copy link
Contributor

  • 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

@imjasonh
Copy link
Contributor

imjasonh commented Apr 1, 2021

@imjasonh
Copy link
Contributor

imjasonh commented Apr 5, 2021

Cancelling this week, let's review #694 today and if you want stickers please let me know 😄

@imjasonh imjasonh closed this as completed Apr 5, 2021
@imjasonh
Copy link
Contributor

Reopening / repurposing this for the April 12 meeting.

@imjasonh imjasonh reopened this Apr 12, 2021
@adambkaplan adambkaplan changed the title April 5th, 2021 Community Meeting April 12th, 2021 Community Meeting Apr 12, 2021
@adambkaplan
Copy link
Member

Update our branch protection rules so we can "float" k8s and golang version: #723

@imjasonh
Copy link
Contributor

EPs:

@adambkaplan
Copy link
Member

Minutes:

  • Parameters EP - needs more feedback related to direction (free form parameters vs. 1st class APIs). The environment variables proposal from @gabemontero will be influenced by our approach here.
  • Twitter account - there is a growing need for credentials to be shared among project maintainers/admins. This applies not just to our twitter account, but things like credentials used in our private git test suite.
  • Removing deprecated fields - we need to ensure that we can do this safely for things that upgrade Shipwright. Example - do we ensure that unknown fields are preserved in etcd? In addition, downstream consumers may depend on current APIs, they need notice before fields are removed.
  • k8s 1.20 bump revealed that some e2e/integration tests include kube versions in their names. If possible, this should be switched to use "latest"
  • Removing PipelineResources - this is not being promoted out of Tekton alpha. EP is up to discuss our path forward.
  • Local source EP - a similar feature is being proposed in Tekton, with a different technical approach. This is an area we can collaborate in. All agree this is a feature Shipwright wants.

@adambkaplan
Copy link
Member

/close

@openshift-ci-robot
Copy link

@adambkaplan: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

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

4 participants