Comment 75 for bug 1990450

@Andreas, sorry for the confusion, let me see if I can help making things a bit easier to understand

We are trying to land the Pro update feature for a while now. Bug #2043425 is a problem reported with the current implementation of the feature. Our PM asked us to not move the current version of the SRU to -updates but to fix 2043425 first, which is why we tagged the current bug as verification-failed (to avoid having it moved to updates).

We can't reuse the same revision with new content so we are adding a new changelog entry with a reference to the issue fixed but that new revision. Since the current version isn't in -updates we built the update with -v$current_updates_version since that's technically the content of what needs to be verified (and the bug here should be verified again to make sure we didn't introduce a regression since the fix was verified in the previous revision), I thought that was common practice?

Since 2043425 is a problem with the changeset of the current -proposed version we could probably have re-used the same bug number here rather than listing an extra reference...

Let me know if the explanations are enough to move forward or if you would prefer to see things changed somehow