Apologies if this has been asked before, I could not find anything related in the issue queue.
I am seeking a method to schedule the publishing of specific revisions of nodes. Scheduler works very well for the nodes themselves, but for our use, where many people collaborate and schedule content for publication all the time, scheduling a specific revision of a node to go "active" is an important feature.
Is it viable to build this feature into the architecture of Scheduler? The UI would need thorough care, so as not to clutter and confuse a user with permissions to schedule revisions. One would also need to consider how many revisions could be scheduled, and how to avoid overlapping scheduling timeframes, and so on.
In short: has anyone considered this as an extension of Scheduler, or are there other more obvious choices that would work alongside?