Skip to content

Remove the link to Zig SDK. #43

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jul 11, 2023
Merged

Remove the link to Zig SDK. #43

merged 2 commits into from
Jul 11, 2023

Conversation

mathetake
Copy link
Contributor

The SDK has been archived, and won't be maintained anymore.

Signed-off-by: Takeshi Yoneda <[email protected]>
Signed-off-by: Takeshi Yoneda <[email protected]>
@@ -18,13 +18,11 @@ Proxy-Wasm extensions across different proxies.
* [C++ SDK]
* [Go (TinyGo) SDK]
* [Rust SDK]
* [Zig SDK]

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @mathetake ,
I'm sorry that you want to remove mention of the Zig SDK, but as the author of it, that is your prerogative. Would you be open to retaining a historical link to it from Proxy-Wasm documentation if it made clear that the SDK is archived and no longer being updated?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1 to leaving it mentioned as "unmaintained" until, hopefully, another version emerges.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sorry, I am planning to delete the repo after communicating to my friend who is using it, not being archived, so it would be just a dead link.

@mathetake mathetake merged commit d2c545b into master Jul 11, 2023
@mathetake mathetake deleted the removezig branch July 11, 2023 03:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants