Separate "publish to QA" from "Released"

[berolinux]

For the rolling release, we need publishing to go to QA, but packages to still go to release/ instead of updates/.

[benbullard79]

Unless I'm mistaken they actually should publish to testing? There are no updates repos for rolling just like for cooker.

[itchka]

The following is a short description of the functionality required for OpenMandriva Qa group to be able to implement QA on the Rolling repository.
The QA tool used for this purpose is kahinah. https://kahinah.rxu.tech/builds/testing.
This tool allows QA to control the flow of packages to the update repository in released versions.
Rolling is different from a released version. The flow of Qa'ed packages needs to be different for rolling. Initially the default repo for publishing after a package is built should be testing. After the package is approved in kahinah it should be moved to the main repo and the package removed from testing. The first part is working ok but what is not happening is that the package is not being removed from testing so the testing repo just gets bigger and bigger until it is maintained manually.