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

Community Meeting September 25, 2024 #52

Closed
robnester-rh opened this issue Sep 11, 2024 · 2 comments
Closed

Community Meeting September 25, 2024 #52

robnester-rh opened this issue Sep 11, 2024 · 2 comments
Labels
community-meeting Community Meeting Agendas

Comments

@robnester-rh
Copy link
Contributor

Overview

At 10am Eastern, 7am Pacific, 2pm UTC; find your time

Video call link: meet.google.com/ved-ivnv-aen

dial-in: (US) +1 409-444-2447‬

PIN: ‪873 550 579#‬

More phone numbers: tel.meet/ved-ivnv-aen?pin=7872592963542&hs=1

Add topics you'd like to discuss below!

@robnester-rh robnester-rh added the community-meeting Community Meeting Agendas label Sep 11, 2024
@lcarva lcarva changed the title Community Meeting September 18, 2024 Community Meeting September 25, 2024 Sep 20, 2024
@lcarva
Copy link
Member

lcarva commented Sep 20, 2024

I'd like to talk about handling breaking changes in data schema, e.g. enterprise-contract/ec-policies#1143. Currently, we have to wait until a certain version of the ec policies is propagated in all the places we care about. Otherwise, using a newly supported attribute may cause data schema failures for some users.

The current approach is ok, but I'd rather not have to stage changes together. Can we think of a simpler way to do this?

We could use some convention, e.g. <key>_v2, to represent this. Is that too heavy handed?

@lcarva
Copy link
Member

lcarva commented Sep 26, 2024

Filed enterprise-contract/ec-policies#1157 as a resolution for the topic above.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community-meeting Community Meeting Agendas
Projects
None yet
Development

No branches or pull requests

2 participants