DemesneGH commented on issue #165: URL: https://github.com/apache/incubator-teaclave-trustzone-sdk/issues/165#issuecomment-2635948721
> * Option 3: Release as v0.4.0, indicating as a major development step. As we see further adoption of Rust based TAs in production environments then only we will be able to know their stability. I agree with you. Let's make the next release 0.4.0. However, since 0.3.0-rc1 did not complete the Apache release process, we may have to keep it as rc1 for now. > We can do releases in say 1 week cadence with OP-TEE releases with a minor version bump say for example `v0.4.0` => `v0.4.1` for the next OP-TEE `v4.6.0` release and so on. The version format follows `MAJOR.MINOR.PATCH`, it's good to sync with OP-TEE's release plan but I'm not sure whether to increment the MINOR or PATCH number. Would the MINOR number be more reasonable? (which means `v0.5.0 for OP-TEE v4.6.0`) -- 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
