I'm in the same boat, having inherited an implementation where "Changed Resources" lists about 60 rules, data elements, and extensions that have non-live changes, and that I'm painstakingly cleaning up. Ability to delete revisions that aren't live in production would be even better, so that I don'...