openSUSE:ALP/Workgroups/Git-Packaging-Workflow/Minutes/20220824

Attendees

Automatic source update in OBS is implemented
- How to implement review mechanics in the light of the package centric view
- For example, in some code streams the same package will be used in embeded devices
- Before merging we should be sure that the change is compatible with those devices
- i.e one code stream will affect other code streams
Create a WG to analyze workflows
- Is there any idea yet how package source in git and source services will work together?
- Client side services, mode manual or disabled, should work.
- buildtime services are also working
- Server side source services, default or serveronly or trylocal mode, are supposed to be not supported. Git source changes should be done via commits.
Alberto reports state of git-notes research
- it creates an own branch referencing a commit from foreign branch and provides text notes
- Alberto wrote a small tool to generate changes files out of the notes
- Problem is the handling of the second branch to be in sync on push and merge requests

AI: all, sync with your teams who should be involved in the review-workflow-workgroup

AI: dirk. setup security & monitoring on the gitea instance
AI: Manuel and Alberto to look at git notes
AI: dirk to create page on changes file discussion
AI: all: start using the git packaging workflow and identify the quirks
AI: help Dan to update documentation on how to use git based packages (add to https://openbuildservice.org/help/manuals/obs-user-guide/ ?)
AI: Adrian and snbarth to see how build status can be reported in the gitea webui for a particular source state