apache / apache/teaclave-sgx-sdk
Hints on migrating to v2.0.0
- Dominant language
- Rust
- Stars
- 1.2k
- Forks
- 268
- PR merge metrics
- No merged PRs in 30d
Description
Very good job on the v2.0.0 release. It looks much nicer to work with!
We would like to migrate our repository from the v1.xx to the v2.0.0-testing branch. I have been looking at the sample code, but I have some questions and assumptions that I would like to confirm:
* In the readme: What does it mean `Most dependencies are use-able without any change.`, what is the criteria for them to be usable?
* Is there a reason the v2.0.0 crypto sample code uses the legacy build mode? Would there be any reason for us to use the legacy build mode?
* Is there something hidden that might prevent us from migrating, or that we need to consider?
Thank you very much for your answers!
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the README migration guidance and the v2.0.0 crypto sample code, especially its legacy build mode. Document the criteria for dependency compatibility, explain whether legacy build mode is needed, and identify migration blockers or considerations for v1.xx users.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100