For reasons beyond my apprehension the following inconsistencies appear with non-packaging repos:
Additionally at least neon/settings has changes in Neon/release which are not merged into master.
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Open | None | T2906 fix neon/fork/whatever repo workflow | ||
| Open | None | T3407 Implement build permutation for shared things |
tidied up the neon/ repos
forks/ repos should share branches for all builds, what would be a better name for a branch than master? Neon/all ?
@jriddell before we adopt Neon/all I would say we need an "all" build permutation. i.e. a thing that gets built once but pushed into all repositories. That's a larger epic though since I think this involves changes in various parts of the tooling. Might well be worth to track this separately?
Yeah, ehm, this is not fixed.
I open a random projects yaml and find:
- forks:
- appstream:
branch: Neon/release
- base-files:
branch: Neon/unstable
- libkolab:
branch: Neon/unstable
- libkolabxml:
branch: Neon/unstable
- live-build:
branch: master
- packagekit:
branch: master
- pyqt5:
branch: master
- aptdaemon:
branch: master
- drumstick:
branch: master