Published environment and published versions for posts/pages to be able to work on the same post/page without affecting the production version until the changes are ready to become the next version of the production post/page.

[oglekler]

Imagine you have several environments - dev, stage and production and you are working on several pages at once. Some of them are ready to be shown to the client and you are deploying code and database to the stage from dev, but some of them are not ready and the client will be unhappy to see unfinished work on the stage, so, you are hiding them for a while and you are starting to reverse changes you did filing that you messed up somewhere.
And then the client is telling you that some of the pages need to be published straight away but others need additional work and to publish a part of the work you've done you are messing further with revisions hoping not to get confused by all this published, unpublished and reversed changes. This leads you to more work and more stress. As a result, you will publish something that isn't ready and lose something that was ready and start to think that you need to change processes to avoid this mess in future.

The solution is to publish a certain version for a certain environment assuming that if the version is published for the production it is also published for stage and dev if there is no later version published for a particular env.

[sabernhardt]

Related: #23314