cancel
Showing results for 
Search instead for 
Did you mean: 

Deployment

kramoutar
Champ in-the-making
Champ in-the-making
So, I recently found out that the publishing the latest snapshot means all content that has been previously approved to the Staging Sanbox will also be published.

However, let's say I have two envs, QAand PROD, which receive content from my Alfresco server.  Content author A makes a content update, destined for QA; it's approved and makes it the Staging sandbox as snapshot 122.  Content author B makes an update that needs to go to PROD ASAP; it's approved to the Staging sandbox as snapshot 123.  Publishing snapshot 123 to PROD means that the QA change approved and snapshotted as 122 will also be deployed to production.

How do I prevent this?

Thanks.
2 REPLIES 2

kramoutar
Champ in-the-making
Champ in-the-making
In reading more about the test servers and workflow for v3.2, there is a key piece I'm missing.

Using my scenario above: Content Author A makes a content update, attaches it to a workflow to be approved.  Is the Content Author or Reviewer responsible for publishing that content to the test servers?

mrogers
Star Contributor
Star Contributor
Whoever wants to use the test server is reposnible for deploying their content to the test server and releasing it when they are finished.