apache / apache/teaclave-sgx-sdk

The new third party forks

Open
#115 15 comments 0 reactions 0 assignees View on GitHub
Dominant language
Rust
Stars
1.2k
Forks
268
PR merge metrics
No merged PRs in 30d

Description

Hi,
First of all I want to say that I really like that you're moving into regular github forks which helps to see the code changes :)

There's one problem though, which is that we use a specific revision of this sdk in order to make sure we're on the right version always and we don't get version bumps without first making sure nothing is broken, but these new forks point to the master branch.

I'm actually not sure what the best solution is, what we do with our forks is have branches which represent the SDK version they're dependent upon.

What do you think?

Thanks,
Elichai.

Contributor guide

No contributing guide indexed for this repository

Research direction

Review the issue's discussion about third-party forks, the master branch, pinned SDK revisions, and version-specific branches. First establish whether the repository has an agreed fork and release-versioning policy; done requires a decided approach that prevents consumers from receiving unintended SDK version changes.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
release
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.