-
-
Notifications
You must be signed in to change notification settings - Fork 75
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
Remove all JSON Schema files after spec 3.0 release #183
Comments
This issue closes #113 as well. |
Hi Jonas I would like to work on this one. |
@jonaslagoni to resolve this issue I need to remove folders like this |
Yes exactly 👍 Remember this will most likely not be merged until after the spec 3.0 release in June 🙂 |
okay so you are saying that this will be merged after spec 3.0 release in June? |
Yes, so you can start the PR up with no problem, but don't expect much activity before that 🙂 |
okay no issues with that. |
This issue has been automatically marked as stale because it has not had recent activity 😴 It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation. There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model. Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here. Thank you for your patience ❤️ |
Still relevant |
This issue has been automatically marked as stale because it has not had recent activity 😴 It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation. There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model. Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here. Thank you for your patience ❤️ |
Reason/Context
After spec 3.0 release all schema files will be located in the spec-json-schema repository, where all codeowners for the bindings will also become codeowners for their respectful bindings.
https://github.com/asyncapi/spec-json-schemas/tree/next-major-spec/bindings
Therefore we need to remove the schema files from this repository.
The text was updated successfully, but these errors were encountered: