Comment # 4 on bug 4572 from timewulf@network-application.de

What about using rpmfusion-update and rpmfusion-update-testing in the
recommended way?

The "old" version (here 58.x.xxxx) stays in rpmfusion-update until the new
packages (59.x.xxxx) are synchronized and correctly working in
rpmfusion-update-testing. Thereafter the old will be replaced by the new for
starting to work on the next changes in rpmfusion-update-testing?

The problem I see is, that both teams don't use the testing repository to
synchronize there work.