Hi All,
The next release of the Firmware-A bundle of projects tagged v2.12 has an expected code freeze date of Nov, 8th 2024.
Refer to the release cadence section from TF-A documentation (https://trustedfirmware-a.readthedocs.io/en/latest/about/release-information...).
Closing out the release takes around 6-10 working days after the code freeze.
v2.12 release preparation tasks start from now.
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 labels 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,
Govindraj R
Hi All,
The next release of the Firmware-A bundle of projects tagged v2.13 has an expected code freeze date of May, 2nd 2025.
In order to accommodate the Linaro connect event occurring during the week of May 12th we may extend the release completion date up until the week of May 26th.
v2.13 release preparation tasks start from now.
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 labels 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.
Regards, Olivier.
Hi,
In preparation to the Firmware-A v2.13 bundle release the following tags were applied to TF-A/TF-A-tests/Hafnium/RMM/OpenCI projects:
https://git.trustedfirmware.org/plugins/gitiles/TF-A/trusted-firmware-a/+/re... https://git.trustedfirmware.org/plugins/gitiles/TF-A/tf-a-tests/+/refs/tags/... https://git.trustedfirmware.org/plugins/gitiles/ci/tf-a-ci-scripts/+/refs/ta... https://git.trustedfirmware.org/plugins/gitiles/ci/tf-a-job-configs/+/refs/t... https://git.trustedfirmware.org/plugins/gitiles/hafnium/hafnium/+/refs/tags/... https://git.trustedfirmware.org/plugins/gitiles/ci/hafnium-job-configs/+/ref... https://git.trustedfirmware.org/plugins/gitiles/ci/hafnium-ci-scripts/+/refs...
https://git.trustedfirmware.org/plugins/gitiles/TF-RMM/tf-rmm/+/refs/tags/tf...
Trees are frozen still accepting security or bug fixes until the release close down happening in 4th or 5th week of May.
To platform owners, please use this tag for building and testing then report any issue before the final tagging.
Thanks & Regards, Olivier.
________________________________ From: Olivier Deprez Olivier.Deprez@arm.com Sent: 04 April 2025 08:55 To: tf-a@lists.trustedfirmware.org tf-a@lists.trustedfirmware.org; tf-a-tests@lists.trustedfirmware.org tf-a-tests@lists.trustedfirmware.org; tfa-lts@lists.trustedfirmware.org tfa-lts@lists.trustedfirmware.org; hafnium@lists.trustedfirmware.org hafnium@lists.trustedfirmware.org; trusted-services@lists.trustedfirmware.org trusted-services@lists.trustedfirmware.org; tf-rmm@lists.trustedfirmware.org tf-rmm@lists.trustedfirmware.org Subject: Firmware-A v2.13 release code freeze notification
Hi All,
The next release of the Firmware-A bundle of projects tagged v2.13 has an expected code freeze date of May, 2nd 2025.
In order to accommodate the Linaro connect event occurring during the week of May 12th we may extend the release completion date up until the week of May 26th.
v2.13 release preparation tasks start from now.
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 labels 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.
Regards, Olivier.
Hi All,
The next release of the Firmware-A bundle of projects tagged v2.14 has an expected code freeze date of Nov, 7th 2025.
Closing out the release takes around 6-10 working days after the code freeze. v2.14 release preparation tasks start from now.
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 labels 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.
trusted-services@lists.trustedfirmware.org
-
Govindraj Raja -
Olivier Deprez