See the example spec here:

https://pagure.io/modulemd/blob/master/f/spec.yaml

We need to handle:

• buildorder in our batches.
• refs of module and rpm deps.
• module inclusion versus module dependency

Anything else?

Also, my expectation is that the modulemd files stored in dist-git wouldn't define the name, stream or version. These should be extracted from the VCS data.

OK - before our next sprint, we should break this card out into 4 separate cards, one for each of those features.

I've created smaller cards about modulemd update and tagged them as "modulemd-1.0". Link to list is here:

https://pagure.io/fm-orchestrator/issues?status=Open&tags=modulemd-1.0

We should support changes in modulemd-1.0 now. Closing.