Koji 1.24.0 is out. Thanks to everyone who contributed!
You can read release notes here:
https://docs.pagure.org/koji/release_notes/release_notes_1.24/
Highlights:
* additional filters to list-tasks command
* querying history based on extra keys
* getNextRelease supports nightly release format
* livemedia supports repos from kickstart and nomacboot
* lowered default multicall batches (would help with some long-running
transactions)
* CGImport now allows only one CG type per import
* external repos can be split by architecture
* plugin hooks for repo modification (allowing repo signing)
* bug fixes
* documentation updates
* 37 pull requests ( + 21 in 1.23.1)
You can view the 1.24 roadmap at https://pagure.io/koji/roadmap/1.24
For the current roadmap, see https://pagure.io/koji/roadmap
You can download this and other releases at https://pagure.io/koji/releases
--
Tomas Kopecek <tkopecek(a)redhat.com>
RHEL Build Development, RedHat
In this issue [1] we want to have some better early parsing of CG metadata
before starting the import. JSON schema looks to be a good way to do that.
I've experimented with it a bit and it raised few questions. It is not a
short file (basic variant about 230 lines and I would like to inject it
with more constraints) so it doesn't seem to be a good idea to put it into
the code directly. Also if it will not be in the code itself (but separate
json) others can use it directly in their CG implementations to precheck
the json before sending it to koji.
My question is what would be the ways you would like to use it? /from that
it should be decided where it should be placed, packaging, etc./
Feel free to comment here or in the issue.
[1] https://pagure.io/koji/issue/2690
--
Tomas Kopecek <tkopecek(a)redhat.com>
RHEL Build Development, RedHat
