To my understanding, next steps are PRservice and RPM repository/ies creation.
do you think you can take can of that task ?
Thanks

Can we publish the RPM repository on AGL server?

What work still needs to be done for this issue?  Can it be closed?

@Walt Miner: can't reproduce on my side, can you reassign this issue?

Let's keep this example in mind for comparison:

• in OBS, each metadata change increases a 'check-in' counter

• each 'rebuild' (due to dependencies) increases a 'rebuild' counter (the counter starts at 1 for each new check-in)

• the rpm revision is set to be "$check-in . $rebuild"

• So even a metadata revert would trigger the check-in counter to increase

Translated to OE:

• we don't have an equivalent for the check-in counter. PRservice is closest but we have the issue on metadata reverts and the PR going backward.

• we don't have a 'rebuild' counter - could PRserv be used to provide this maybe ?

... story continues ...