The productmd-compose spec lists these examples for the compose type:
- rel-eng - nightly - testing - updates - released
But almost none of these is a real compose type. Compose types are formally defined in productmd: the types that exist are 'test', 'ci', 'nightly' and 'production'. Unless I'm missing something, I think the examples here should be corrected (and perhaps a link to productmd included). @lholecek
Thanks Adam, ping @pholica maybe we should extend composeinfo, as these you used are quite used on downstream?
You're right. The names that are there right now are less formal and could be historical. I'm thinking that we may need to include also label name as (Beta, Snapshot, RC, Update) as those are needed to distinguish between e.g. "production"/"Update" and "production"/"Snapshot" which we intended to mark as updates and rel-eng. Such change unfortunately won't allow having transition period :/
Yeah, label name could be important too. Fedora has the same pattern, in fact - we also have update composes that are 'production' type, but have labels like 'Update-20190614.0057'. They also have a 'release' dict in the payload metadata, the stuff in there may be significant too I guess. See e.g. https://kojipkgs.fedoraproject.org/compose/updates/Fedora-30-updates-testing-20190614.0/compose/metadata/composeinfo.json
So far as transition period goes - is something besides openQA now emitting productmd-compose messages? IIRC I wrote the original spec and openQA was the only thing using it at the time...
productmd-compose
@adamwill .. just on downstream the team testing composes is exposing them ... we use the same specs there ... @pholica is the guy
Login to comment on this ticket.