Agenda

Antitrust Policy

• Action Items Review

• Meeting next week, Cancelled due to Kubecon

• Meeting on 2026-04-01, @Fiachra Corcoran will chair

• Proposed Branching Strategy

  • Switch branching strategy to have a maintenance 1.5 branch for the existing Porch

  • Merge feature-1.6 to main and continue the main development on main, bringing in new changes there. So main would be released as 1.6.x for Nephio R7

  • If necessary we do CVE updates/bug fixes or urgent small changes on the 1.5 branch and do 1.5.x releases off this branch, this branch will not get any major new functionality

  • We will provide an upgrade path from 1.5.x to 1.6.x

• More meaningful error messages

  • @Viresh Navalli will take a look at https://github.com/nephio-project/porch/pull/272 ,

• PR Review

• AOB

Minutes

Create Remote Fetches

• https://github.com/nephio-project/porch/pull/246 Will be documented as an issue by @Gergely Nagy

Enable go-git caching

• https://github.com/nephio-project/porch/pull/368 by @Gergely Nagy, this PR is now up for review, please check/test the PR. It is being tested by @Kushal Harish Naidu, so far so good, it gives a small improvement without any side effects.Action items

• This looks fine in testing by @Kushal Harish Naidu , it should be OK to merge.

Webhooks for Deletion

• Are Webhooks inherently slow, will this cause problems for the CRD PackageRevision work?

  • Why is the package deletion slow? It might need to list all the PRs?

  • Maybe don’t use validation int he webhook and don’t do it

  • @Fiachra Corcoran to raise issue on this.

Should we remove CR Cache?

• CR Cache makes the implementation more complex

  • PackageRev/PackageRevision tracking for consistency

  • Webhook for PackageRevision deletion has a 30 second timeout (even though we have a 290 second timeout in the API server)

• Should the CR cache be deprecated first and then removed? That would be the proper approach.

• In the PackageRevision CRD work we don’t need the PackageRev CRD any more

  • PackageRev CRD won’t be needed once we have the PackageRevision CRD

  • Will we need a CR cache at all then?

• Let’s work out the design of the PackageRevision CRD epic first and then see where we stand with the CR cache.

• Using the PackageRevision CRD directly towards a git backend is in effect the same as the CR cache we have today

• @Gergely Nagy to raise an issue on this

Proposed Branching Strategy

• Agreed.

• Documentation versioning strategy will need to be worked out.

More meaningful error messages

• @Viresh Navalli , @Catalin Stratulat and @László Mózes will formulate a new issue to capture the spirit of this PR to guide @Viresh Navalli in this work.

DB Cache pushes draft PRs to git

• https://github.com/nephio-project/porch/pull/403

• Should this be enabled in the CI?

  • We should turn this on in the DB cache CI run @Rendre Greyling will turn the option on in the DB cache CI.

• go-git can be optimized to make it more performant (Will be in a separate PR)