Releases for revisions

[dameert]

Why

When comparing environments, sometimes only a subset of data needs to be published. When environments are not synced, or when many maintainances are ongoing, the risk of error is growing. Therefore we should be able to attach revisions to a release, and publish (apply) that release to an environment.

How

As discussed with Mathieu:

• No changes in the UX when creating and editing content revisions
• Have an admin view "Releases" in which
  • new releases can be created
  • existing releases can be applied to an existing environment
  • a release can be reverted

Create a new release

• Chose a name and add revisions to your release.
• By default all content is shown to be selected, showing the most recent changed revisions first. Only revisions in their default environment are available to select.
• Facets are available to filter on content type.
• Search field is available to filter (at least introducing the ouuid of a revision should work)

Apply a release

• Select an environment to apply the release to.
• If the selected environment is the default environment of a release, nothing happens
• if the selected environment is another environment, the revision in the default environment will be published to that environment
• Save this action to allow for a revert
  • Store database ID of every revision that was originally in the "to" environment

Revert the application of a release

• Select an applied release to rollback
• Verify for every stored database ID that it is still available (with revision_to date null) --> This might not be a good check!
• If the rollback is possible: apply it
• Else generate an error message that rollback is not possible

[dameert]

As for the "revert" check:

• Check that all the revisions of the release are still present in the "To" environment
• Check that all the reveisions overriden by the release are still available in EMS.

[IsaMic]

Status now: we have

Add Release Form with

• name
• execution Date (for a schedule)
• environment source
• environment target
• ( and status => Wip, Ready, Apply, Scheduled, Canceled, rollback ?? create status = wip .)

Index Release (Entity table) column:

• name
• executionDate
• status
• env source
• env target
• Actions : Edit, delete, Add revisions to release, Publish release (immmediate use alignRevision of publishService)

EntityTable Revisions (add to or delete from release) (EntityTable one for add and another for delete) : column

• label
• content type
• use minrevId from align environment (date + user of revision of source)
• use maxrevId from align environment (date + user of revision of target)

We need yet :

• Adapt alignRevision of publishService to save a revision before publish or unpublish(archive) (to use on rollback)
• Action to publish (cron)
• finalized draft - event to detect if revision already in release and ?
• revision already in other release ?
• manage different status on release ( Wip, Ready, Apply or applied, Scheduled, Canceled, rollback ou rollbacked)
• Limit with user role (actually defined in menu publish but role Align Environment ? )
• Rollback
• In revision add button to Add or create a release
• duplicate release ... other?

Questions about what already exist.

Status Wip, Ready, Apply, Scheduled, Canceled, rollback :
I imagine, when status is WIP : I can edit release, delete a release, add or removes revisions but I can't do publish release. need to defined others