DemesneGH commented on issue #165: URL: https://github.com/apache/incubator-teaclave-trustzone-sdk/issues/165#issuecomment-2646859519
Thanks for all comments on this thread. Considering Rust's best practices, Apache release processes, OP-TEE’s schedule, and user-friendliness, I propose the following release versioning and schedule: ## Versioning Strategy ### Version Bump - **optee-*** crates*\*: All optee-related crates ([crates.io search](https://crates.io/search?q=optee)) located in `optee-utee/`, `optee-teec/`, `optee-utee-build/` will have synchronized versions and be updated simultaneously. - **Bump criteria**: (quarterly check) && (code changes in any of the `optee-*` crate source code) - **Examples/Projects**: Will be versioned separately and updated independently when their respective code changes. ## Release Process ### optee Rust Crates Release - The optee Rust crates will be published on `crates.io`. - A new version will be released only when new features, fixes, or OP-TEE compatibility adjustments require code changes. - To ensure clarity and encourage synchronized usage, all `optee-*` crates ([crates.io search](https://crates.io/search?q=optee)) will have their versions bumped together, even if some remain unchanged. ### Apache Release for the Entire Repository (follow the [Teaclave Release Guide](https://teaclave.apache.org/docs/release-guide/)) - An Apache release will be made only when a new `optee-*` Rust crate version is published. - The Apache release version will always align with the `optee-*` crates version number. - The source code for all repositories will be packaged and made available in GitHub Releases. - A release note will be included. - The release process will follow voting procedures within the Teaclave community and the Apache Incubator. ## Release Schedule ### Quarterly Release Check - One week after OP-TEE releases a new version, we will verify compatibility with the latest OP-TEE release. - If any `optee-*` Rust crates require updates, a new release will be published after the necessary code updates, and the version numbers will be incremented accordingly. - If there are no code changes in the `optee-*` crates (e.g., only examples/projects are updated), no new release will be made to avoid redundant version bumps. ### Release Record Table To maintain transparency and clarity, we will maintain a table in the main `README` to track release versions and their corresponding OP-TEE versions: | Apache Teaclave SDK Release Version | optee-\* Rust crate Release version | OP-TEE Version | OP-TEE Release Date | Check for Teaclave SDK Release | | ----------------------------------- | --------------------------- | -------------- | ------------------- | ------------------------------ | | - | - | OP-TEE 4.8.0 | 17/Oct/25 | 31/Oct/25 | | - | - | OP-TEE 4.7.0 | 11/Jul/25 | 25/Jul/25 | | - | - | OP-TEE 4.6.0 | 11/Apr/25 | 25/Apr/25 | | v0.4.0 | v0.4.0 | OP-TEE 4.5.0 | 17/Jan/25 | 17/Feb/25 | #### Example Scenario If there are no changes to `optee-*` crates between OP-TEE 4.5.0 and 4.6.0, but changes are made before OP-TEE 4.7.0, the table will appear as follows: | Apache Teaclave SDK Release Version | optee-\* Rust crate Release version | OP-TEE Version | OP-TEE Release Date | Date of Check for Teaclave SDK Release | | ----------------------------------- | --------------------------- | -------------- | ------------------- | -------------------------------------- | | - | - | OP-TEE 4.8.0 | 17/Oct/25 | 31/Oct/25 | | v0.5.0 | v0.5.0 | OP-TEE 4.7.0 | 11/Jul/25 | 25/Jul/25 | | v0.4.0 (no new release) | v0.4.0 (no new release) | OP-TEE 4.6.0 | 11/Apr/25 | 25/Apr/25 | | v0.4.0 | v0.4.0 | OP-TEE 4.5.0 | 17/Jan/25 | 17/Feb/25 | Let's dicuss this proposal, please feel free to comment on this thread, thanks! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
