Technical Meeting 2026-07-01 #4607

liamfallon · 2026-07-01T06:50:43Z

liamfallon
Jul 1, 2026
Maintainer

Attendance

@liamfallon chaired the meeting.

## Github performance

Should we consider an alternative to Github?
There are no hard rules to use Github but it is the best supported platform
Let's kick this to the community meeting next week as a topic.
2025-05-27: The CI test reliability seems to have improved due to the actions we have taken.
2026-06-03: @CsatariGergely to check with CNCF if it is mandatory to use GitHub as a development platform
2026-06-10: No Progress
2026-06-17 to 2026-07-01: No answer yet from CNCF

We will continue to use the custom condition type in kpt rather than the k8s one
We should check duplicate types across Porch and kpt and see if there is some cleanup required. @liamfallon to come back next week on this.
2026-06-10 to 2026-07-01: No Progress

Let's go ahead and test it (1.6.0-test)
2026-06-27: There is a PR to verify releases, it needs to be merged first: Add release artifact verification step porch#1066
2026-07-01: Test of Porch v1.6.0-pre1 was successful and v1.6.0 was released.
@liamfallon to update the release notes to call out the highlights of v1.6.0

This will be very useful
We need to test it, we should merge feat(set-labels): migrate to SDK v1.0.4 with WithDocs support krm-functions-catalog#1258 and merge the catalog PR
Try the catalog github action with the new set-labels function
2026-06-24:
Create GitHub action for bumping patch versions krm-functions-catalog#1259 can be merged now because Build a simple e2e test tool for function catalog #1259 is merged
The solution could be useful in other repos as well
2026-07-01:
This is merged now and working very nicely!
Follow up issue was opened to generate release notes for just the updated functions: Generate notes for only the function bumped by the manual release action #4603
Close this next week.

On hold for now.
The parallel function runner is implemented
We need some days together to come up with an architecture for the next 2-3 years
2026-06-24: Bump discussion to community meeting
2026-07-01: @CsatariGergely will add it to the agenda for next week's community meeting

We'll release the API at v1.0.0 and see if it works
Can we delete v1.3.0 of the API: https://pkg.go.dev/github.com/nephio-project/porch/api
2026-07-01:
API is released
We need to file a request to delete v1.3.0, see https://pkg.go.dev/about#removing-a-package, @liamfallon will do this.

lint/FOSSA/Snyk are all OK
SonarCloud: Working fine in Porch, it needs to be set up on the other repos @CsatariGergely / @efiacor to look into this
Release checker: Works on Porch in PR (not merged yet) Add release artifact verification step porch#1066
CoPilot:
We want it to only trigger on the first push.
It is really pedantic, causing lots of repeated reviews.
Should we trust the the humans?
2026-07-01: Let's roll out the Porch setup to the other repos and leave this for now.

@mozesl-nokia has been testing https://usegitai.com/
It aggressively pushes a lot of metadata onto PRs
Pushing metadata onto PRs in the public may have consequences for security, privacy etc
The metadata is "invisible" unless you go looking for it but if you do look for it, it is extensive
It could help with statistics, it can do a line by line analysis showing what was done by AI, what was done by a human, and what was done by other tools
For now, let's turn AI tracking off and seek guidance on this from the CNCF and others.