qa-tagger appears to require qastaging to be running in order to determine which revno is deployed. This prevents the deployment report from being updated, even though other elements of that report may have changed (i.e. bug tags changing).
The deployment report is the best place to monitor QA status, so the release manager's job becomes harder when the report stops updating. It would be better to use the last deployed revno when the current deployed revno cannot be determined.
qa-tagger appears to require qastaging to be running in order to determine which revno is deployed. This prevents the deployment report from being updated, even though other elements of that report may have changed (i.e. bug tags changing).
The deployment report is the best place to monitor QA status, so the release manager's job becomes harder when the report stops updating. It would be better to use the last deployed revno when the current deployed revno cannot be determined.