Hi,
We plan to change the release policy for the LTS branch to release every Friday. Initially, we wanted to create a release for every logical patch that was merged. But, the release process consumes more cycles than anticipated, and we feel that there is an opportunity to fine-tune the policy.
This does not impact the speed at which the patches are merged to the LTS branch but reduces the release work. So, the patches will get merged as soon as all the requirements are satisfied, but the actual release (version bump, release notes, tag creation) will be done on a Friday.
Please let us know if there are any concerns with this approach.
Thanks.
Hi,
Commit 327f4bb0cf20 ("fix(el3_runtime): allow SErrors when executing
in EL3")[1], seems disruptive for LTS branch at this stage. Therefore
we, the LTS maintainers, propose to revert it in the lts-v2.8 branch.
The reason is that if a misbehaving binary is running in a lower EL,
e.g. one which has external aborts masked while executing instructions
which cause SErrors, then it's possible for those SErrors to be
received by EL3 even if they weren't caused by it. This is a change in
the contract between EL3 and lower ELs, that existed at the time when
TF-A v2.8 was released. LTS 2.8 is based on TF-A 2.8.
Revert patch, which is not yet submitted, can be found here[2]. If you
have any comments or objections please share before the end of Friday
24th February Pacific Time. We'll merge it after that.
Thanks,
Okash
[1] https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/18953
[2] https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/19094
Hello,
We have identified the following patch as a candidate for the lts-v2.8 branch.
* fix(zynqmp): enable A53 workaround(errata 1530924) (I251ffe3c) * Gerrit Code Review (trustedfirmware.org)<https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/19531>
The patch satisfies the merge criteria initially outlined in the guidance doc and will be merged soon. Please provide feedback or comments on gerrit.
Thanks.
