Hi community, It seems this vote has been pending for some time. This email aims to first explain the reason for re-tagging RC1, and then kindly request the verification and vote on the release.
---- A few clarifications regarding this RC1: The previous RC1 was tagged before our graduation on Aug 21, aligned with the OP-TEE release schedule. Since we were in the final stage of graduation at that time, we planned to start the vote afterward; this is the first mail of the thread (Sep 5). As Zhaofeng raised some concerns, I have re-tagged the release to the latest main branch (which fixed the DISCLAIMER), includes significant new features and code changes (https://github.com/apache/teaclave-trustzone-sdk/compare/102e65ee480746d8070636ac9a7376dc8d759c37...ad670a1f28e77884d652e20427aa64c41213175a) , not just minor fixes. Therefore, I restarted it as a new RC1 rather than RC2. Since this release happens to coincide with the final stage of our graduation, the above note explains the process of handling this release candidate and I'd like to proceed to finish the release based on the current rc1 (in mail of Sep 8). If this approach is not acceptable or if there are other concerns about this release—please feel free to share your input. ---- Anyway, our 0.6.0 RC1 is now ready for verification. I would appreciate your help in checking this release: Just copy and paste the following steps to verify artifacts: ``` $ wget -qO - https://downloads.apache.org/teaclave/KEYS | gpg --import $ wget https://dist.apache.org/repos/dist/dev/teaclave/trustzone-sdk-0.6.0-rc.1/apache-teaclave-trustzone-sdk-0.6.0.tar.gz \ https://dist.apache.org/repos/dist/dev/teaclave/trustzone-sdk-0.6.0-rc.1/apache-teaclave-trustzone-sdk-0.6.0.tar.gz.asc \ https://dist.apache.org/repos/dist/dev/teaclave/trustzone-sdk-0.6.0-rc.1/apache-teaclave-trustzone-sdk-0.6.0.tar.gz.sha512 $ sha512sum -c apache-teaclave-trustzone-sdk-0.6.0.tar.gz.sha512 $ gpg --verify apache-teaclave-trustzone-sdk-0.6.0.tar.gz.asc apache-teaclave-trustzone-sdk-0.6.0.tar.gz ``` The simplified building process if you'd like to help to test: ``` $ tar zxvf apache-teaclave-trustzone-sdk-0.6.0.tar.gz $ cd apache-teaclave-trustzone-sdk-0.6.0 $ docker run -it --rm \ -v $(pwd):/root/teaclave_sdk_src \ -w /root/teaclave_sdk_src \ teaclave/teaclave-trustzone-emulator-nostd-optee-4.7.0-expand-memory:latest # Inside the docker container: root@xxxx:~/teaclave_sdk_src# make ``` I have verified the artifact signatures and successfully built the release from source. I would greatly appreciate everyone’s participation in this vote. Thank you! Best, Yuan Zhuang Apache Teaclave PMC On Mon, Sep 8, 2025 at 8:35 PM Yuan Zhuang <[email protected]> wrote: > > Apologies for sending the previous message from the wrong email > address. I am resending this email to confirm that the above content > should come from my Apache address ([email protected]). > > On Mon, Sep 8, 2025 at 8:26 PM 庄园 <[email protected]> wrote: > > > > Hi all, > > > > As discussed above, I have re-tagged the code and re-packed the > > release without the “incubating” text in the source code. > > Also, the docker image for building from source is updated. > > > > The release note is available in: > > - https://github.com/apache/teaclave-trustzone-sdk/releases/tag/v0.6.0-rc.1 > > > > The release candidate to be voted over is available at: > > - https://dist.apache.org/repos/dist/dev/teaclave/trustzone-sdk-0.6.0-rc.1/ > > > > The release candidate is signed with a GPG key available at: > > - https://downloads.apache.org/teaclave/KEYS > > > > Instructions to verify the release candidate’s signature: > > - https://teaclave.apache.org/download/#verify-the-integrity-of-the-files > > > > The release artifacts have passed all GitHub Actions CI checks. You > > can also reproduce the build process manually from source using the > > following commands: > > > > ```bash > > $ wget > > https://dist.apache.org/repos/dist/dev/teaclave/trustzone-sdk-0.6.0-rc.1/apache-teaclave-trustzone-sdk-0.6.0.tar.gz > > $ tar zxvf apache-teaclave-trustzone-sdk-0.6.0.tar.gz > > $ cd apache-teaclave-trustzone-sdk-0.6.0 > > $ docker run -it --rm \ > > -v $(pwd):/root/teaclave_sdk_src \ > > -w /root/teaclave_sdk_src \ > > > > teaclave/teaclave-trustzone-emulator-nostd-optee-4.7.0-expand-memory:latest > > # Inside the docker container: > > root@xxxx:~/teaclave_sdk_src# make > > ``` > > > > The vote will be open for at least 72 hours. Anyone can participate > > in testing and voting, not just committers, please feel free to try > > out the release candidate and provide your votes to this thread > > explicitly. > > > > [ ] +1 approve > > [ ] +0 no opinion > > [ ] -1 disapprove with the reason > > > > > > Best, > > > > Yuan Zhuang > > Apache Teaclave PMC > > > > On Fri, Sep 5, 2025 at 10:32 PM Zhaofeng Chen <[email protected]> wrote: > > > > > > Thanks for arranging the release. > > > > > > As this is the first release after graduation, we might need a few > > > adjustments compared to the incubator process. In particular, the release > > > artifact still contains an incubator DISCLAIMER file. We already have > > > commit `ebe5f5` to remove the DISCLAIMER along with other adjustments. > > > Could you please tag the release after that commit and launch a new vote? > > > > > > For build reproducibility and testing, can we use the official Docker > > > image > > > (teaclave/teaclave-trustzone-emulator-*)? This image can build the SDK > > > example source without downloading dependencies, which saves a lot of time > > > for PMCs willing to perform the checks. > > > > > > Best, > > > Zhaofeng > > > > > > > > > > > > > > > On Fri, Sep 5, 2025 at 5:51 PM Yuan Zhuang <[email protected]> wrote: > > > > > > > Hi all, > > > > > > > > I am pleased to call the vote for the release of Apache Teaclave > > > > TrustZone SDK 0.6.0 (rc.1). > > > > > > > > This is our first release vote since graduation. Many thanks to our > > > > mentors, PMCs, committers, and contributors for your continuous > > > > support and efforts, which have enabled the community to grow and > > > > successfully graduate to a top-level project! > > > > > > > > Same as previous releases, the information is as follows: > > > > > > > > The release note is available in: > > > > - > > > > https://github.com/apache/teaclave-trustzone-sdk/releases/tag/v0.6.0-rc.1 > > > > > > > > The release candidate to be voted over is available at: > > > > - > > > > https://dist.apache.org/repos/dist/dev/teaclave/trustzone-sdk-0.6.0-rc.1/ > > > > > > > > The release candidate is signed with a GPG key available at: > > > > - https://downloads.apache.org/teaclave/KEYS > > > > > > > > Instructions to verify the release candidate’s signature: > > > > - > > > > https://teaclave.apache.org/download/#verify-the-integrity-of-the-files > > > > > > > > The release artifacts have passed all GitHub Actions CI checks. You > > > > can also reproduce the build process manually from source using the > > > > following commands: > > > > > > > > ```bash > > > > $ wget > > > > https://dist.apache.org/repos/dist/dev/teaclave/trustzone-sdk-0.6.0-rc.1/apache-teaclave-trustzone-sdk-0.6.0.tar.gz > > > > $ tar zxvf apache-teaclave-trustzone-sdk-0.6.0.tar.gz > > > > $ cd apache-teaclave-trustzone-sdk-0.6.0 > > > > $ docker run --rm -it -v$(pwd):/teaclave-trustzone-sdk -w \ > > > > /teaclave-trustzone-sdk yuanz0/teaclave-trustzone-sdk:ubuntu-24.04 \ > > > > bash -c "./setup.sh && (./build_optee_libraries.sh optee) && source \ > > > > environment && make && (cd ci && ./ci.sh)" > > > > ``` > > > > > > > > The vote will be open for at least 72 hours. Anyone can participate > > > > in testing and voting, not just committers, please feel free to try > > > > out the release candidate and provide your votes to this thread > > > > explicitly. > > > > > > > > [ ] +1 approve > > > > [ ] +0 no opinion > > > > [ ] -1 disapprove with the reason > > > > > > > > > > > > Best, > > > > > > > > Yuan Zhuang > > > > Apache Teaclave PMC > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: [email protected] > > > > For additional commands, e-mail: [email protected] > > > > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
