Allow unpublished page versions to be synchronized
Currently, only published page versions (i.e. a major version, such as v1.0, v2.0, etc.) can be synchronized to a target server. When the current working version is a minor version (such as v0.7 or v1.3) and the content is synchronized, only the last major version is synchronized, which means that no changes made since the content was last published will be synchronized. If the content has not yet reached v1.0, the original version (v0.1) is published. Also, setting a Publish From date to some point in the future and clicking the Publish button does not promote the content to a major version - it remains in a minor version until the Publish From date has been reached. Synchronizing the content in that state is pointless, since only the last major version is synchronized. This design defeats the purpose of having a staging environment where content can be created, edited, approved and scheduled for publishing prior to synchronizing to the production environment.
In our case, we have 3 staging sites and 3 production sites, some with multiple cultures. Content is initially created in U.S. English and goes through several revisions before being synchronized to the production site and the other staging sites for translation and publication. The content is created well in advance of the publishing date, and must not go live until a specific date and time. Through painful trial-and-error, we've learned that we must publish content in our staging environment, archive it, synchronize it to the production environment, then create new versions of the content in production to set the Publish From dates to the desired date and time. There are usually several other supplemental content updates that must be made to existing content requiring the same tedious process.
To summarize, we'd like the ability to synchronize any content at any point to the target server(s) and have the Publish From dates respected.