Merge main back to pi (normal and emergencies)

Note: currently is under development, needed manually to ensure to pass the module and dependencies versions from main to pi.

NOTE: if publishing a emergency release during release process of a normal release, then not needed to do the merge of tags form main to pi, since when done this merge for the normal release this will automatically done.

Push the automation tag (normal & emergency)

automation/pi-mobile is branched to backports path for all release of retail.

For normal releases the pi-mobile need to tagged (mandatory)

For emergeny if any new changesets in retail/backports/3.0RRyyQn.x/pi-mobile and retag the existing 3.0RRyyQn.

Example : Current release is 16Q2.2 and there are new changesets in retail/backports/3.0RR16Q2.1/pi-mobile, it is must to retag 3.0RR16Q2 to include the new changesets.

Mantis (normal and emergencies)

Create a new target versions of the type of the just published. Idea is that should be two actives branches in each thread. For example should be 2 normal released available, 2 target versions of q1.x and 2 target versions of q3.x.

Release notes (normal and emergencies)

If was needed to do any transplant, remember to recreate the fixed issues section in the release notes