As a Site Template Administrator: template propagations are run completely in the background and background tasks are executed in a sequence. The LAR from the Site Template export is cached, so different Sites can reuse it.

• LayoutSetPrototypeMergeBackgroundTaskExecutor always uses the latest Template version for the propagation.
• If there is already a queued background task for the Site, we don’t create a new one.
• If there is a background task in progress, we only create a new background task if the Template was modified.

Two new configuration options were added:

• The first one gives the users the chance to automate an existing feature, which improves performance.
• The other one is about displaying the Advanced Staging configuration screen to the users, improving usability.

This is the Staging related implementation of a bigger change. On the Staging side, the LXC Client extensions (Remote apps) could be handled. To make this feature completely working, LPS-182183: Export/Import of FrontEnd Client Extensions is also needed.

• Deletion of property upgrade.log.context.name. Now all upgrade related log lines are automatically tagged with the key upgrade.component, which provides more meaningful information.
• Upgrade Report is now compatible also with upgrade on startup, and it can be printed as Log Thread Context information.
• Upgrades log the result and the type of upgrade that has taken place after all the upgrade processes finish.
• New mBean available with upgrade on startup to obtain real time information about the status and the result of the upgrade.