Hi,
In preparation to the Firmware-A v2.10 bundle release the following TF-A/TF-a-tests/RMM/Hafnium trees were just tagged:
https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git/tag/?h=v2.10-rc0 https://git.trustedfirmware.org/TF-A/tf-a-tests.git/tag/?h=v2.10-rc0 https://git.trustedfirmware.org/ci/tf-a-ci-scripts.git/tag/?h=v2.10-rc0 https://git.trustedfirmware.org/ci/tf-a-job-configs.git/tag/?h=v2.10-rc0 https://git.trustedfirmware.org/TF-RMM/tf-rmm.git/tag/?h=tf-rmm-v0.4.0-rc0 https://git.trustedfirmware.org/hafnium/hafnium.git/tag/?h=v2.10-rc0 https://git.trustedfirmware.org/ci/hafnium-ci-scripts.git/tag/?h=v2.10-rc0 https://git.trustedfirmware.org/ci/hafnium-job-configs.git/tag/?h=v2.10-rc0
This is a call for partners to test those trees on (downstream) platforms and spot any potential issue during the release close down (from now and for the coming week) and before the final tagging.
Thanks & Regards, Olivier.
________________________________ From: Olivier Deprez Olivier.Deprez@arm.com Sent: 29 September 2023 18:32 To: tf-a@lists.trustedfirmware.org tf-a@lists.trustedfirmware.org; tf-a-tests@lists.trustedfirmware.org tf-a-tests@lists.trustedfirmware.org; hafnium@lists.trustedfirmware.org hafnium@lists.trustedfirmware.org; tf-rmm@lists.trustedfirmware.org tf-rmm@lists.trustedfirmware.org Subject: Firmware-A v2.10 release code freeze notification
Hi All,
The next release of the Firmware-A bundle of projects tagged v2.10 has an expected code freeze date of Nov, 7th 2023.
Refer to the Release Cadence section from TF-A documentation (https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git/tree/docs/about/...).
Closing out the release takes around 6-10 working days after the code freeze.
Preparations tasks for v2.10 release should start in coming month.
We want to ensure that planned feature patches for the release are submitted in good time for the review process to conclude. As a kind recommendation and a matter of sharing CI resources, please launch CI jobs with care e.g.:
-For simple platform, docs changes, or one liners, use Allow-CI+1 label (no need for a full Allow-CI+2 run).
-For large patch stacks use Allow-CI+2 at top of the patch stack (and if required few individual Allow+CI+1 in the middle of the patch stack).
-Carefully analyze results and fix the change if required, before launching new jobs on the same change.
-If after issuing a Allow-CI+1 or Allow-CI+2 label a Build start notice is not added as a gerrit comment on the patch right away please be patient as under heavy load CI jobs can be queued and in extreme conditions it can be over an hour before the Build start notice is issued. Issuing another Allow-CI+1 or Allow-CI+2 label will just result in an additional job being queued.
Thanks & Regards,
Olivier.