Thanks, Gary, and to everybody who contributed to this release!

I’d like to quickly remind everybody that, as part of the v2.5 release, the Trusted Firmware-A project formally adopted the Conventional Commits v1.0.0 specification to enable us to radically reduce our time-to-release in the future. Thank you to everybody who took part in the discussions that allowed us to integrate this, and to those whose concerns I hope we have by now satisfied.

As part of this effort, we have introduced a commit verification check to the existing Gerrit-triggered CI job. Where before this applied only to Arm employees, this now includes everybody (even you, reader of this email). This will no doubt require some initial mental reorientation as it did for our Arm-based guinea pigs, but I hope that this it will become a non-issue in short time.

To aid in the transition, we are also now packaging additional tooling, namely Commitizen and commitlint, to make writing conformant commits easier, the installation instructions for which have been integrated into the v2.5 prerequisites page. These tools are optional, but highly recommended if you do find your commits being rejected by the CI.

Please note that patches currently awaiting review on Gerrit will need to adhere to this specification before merging (this should only take a minute).

If you missed previous communications or are unfamiliar with Conventional Commits, here is a brief summary of the format that commit messages are now expected to take:

<type>[optional scope]: <description>

[optional body]

[optional footer(s)]

Where the <type> is one of:

• feat: A new feature
• fix: A bug fix
• docs: Documentation only changes
• style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
• refactor: A code change that neither fixes a bug nor adds a feature
• perf: A code change that improves performance
• test: Adding missing tests or correcting existing tests
• build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
• ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
• chore: Other changes that don't modify src or test files
• revert: Reverts a previous commit

And the [optional scope] consists of an optional parentheses-wrapped scope of your choosing, similarly to how many contributors prefixed their commits previously.

A real-world example:

    docs(prerequisites): add `--no-save` to `npm install`

    To avoid the mistake fixed by the previous commit, ensure users install

    the Node.js dependencies without polluting the lock file by passing

    `--no-save` to the `npm install` line.

    Change-Id: I10b5cc17b9001fc2e26deee02bf99ce033a949c1

    Signed-off-by: Chris Kay <chris.kay@arm.com>

If you have the time, please do read up on the specification for additional details – I promise it’s short.

So long, and happy committing. 😊

Regards,

Chris

From: TF-A <tf-a-bounces@lists.trustedfirmware.org> on behalf of Gary Morrison via TF-A <tf-a@lists.trustedfirmware.org>
Date: Thursday, 20 May 2021 at 15:59
To: tf-a@lists.trustedfirmware.org <tf-a@lists.trustedfirmware.org>
Subject: [TF-A] Trusted Firmware version 2.5 is now available

Trusted Firmware version 2.5 is now available and can be found here:

https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git/tag/?h=v2.5
https://git.trustedfirmware.org/TF-A/tf-a-tests.git/tag/?h=v2.5
https://git.trustedfirmware.org/hafnium/hafnium.git/tag/?h=v2.5
https://git.trustedfirmware.org/ci/tf-a-ci-scripts.git/tag/?h=v2.5

Please refer to the read-the-docs and change log for further information.

Regards,
Gary Morrison -- Arm
--
TF-A mailing list
TF-A@lists.trustedfirmware.org
https://lists.trustedfirmware.org/mailman/listinfo/tf-a