Overlays Meeting (2025-10-21) #172
Replies: 4 comments
-
|
v1.1-dev branch and a new Copy Action #150 |
Beta Was this translation helpful? Give feedback.
-
|
Adding: |
Beta Was this translation helpful? Give feedback.
-
|
Taking notes from the meeting: Auto-merge from main to dev(what we have in OAI specification), too complicated for overlays. Mostly caused by the fact that OAI has the version specs files. We'd like a simpler setup if we want to automate that. @ralfhandl to look into this simpler setup. We need to achieve traceability, and keep the commit history to understand better why any given change was made. A simpler setup would be to do away with dev branches all together and use git's native capabilities. And use tagging for the version releases. |
Beta Was this translation helpful? Give feedback.
-
copyReviewed the copy proposal at #150, mostly in agreement except for a few minor items that I'll add as comments on the PR shortly. There's some work in terms of branching (see previous comments) before we can merge this. Additionally, the ask is to look around for other things that would fit into a minor release, and we want to socialize it as a "last call before 1.1", but we don't want to hold this for too long as it's a nice incremental change that's easy to pick up for implementers. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
This discussion is about a meeting of the OpenAPI Overlays group. We meet on alternate Tuesdays at 08:00 Pacific time, and this is a public meeting.
Meeting link: https://zoom-lfx.platform.linuxfoundation.org/meeting/99628896838?password=f3ff9796-d6a0-4749-b39e-93dc7eafe7cd
This meeting is covered by the OpenAPI Initiative Code of Conduct.
Add comments to this discussion to add items to the agenda for the meeting.
Beta Was this translation helpful? Give feedback.
All reactions