You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello to all developers who use WAMR. We decided to migrate the code related to app-framework to an independent repository wamr-app-framework under bytecodealliance.
Before we go into the details, we apologize for any inconvenience this may cause to developers using WAMR. If you are using the app-framework related code for your business, this action may have an impact on your operations.
There are two reasons why we decided to separate the wamr-app-framework from the wamr:
The current directory structure of wamr is quite complex, which makes document management burdensome and brings additional learning costs to some developers using WAMR.
This decision was made based during the WAMR TSC meeting after discussions and we will migrate the code related to the app-framework to an independent repository.
What will be migrated out:
The text was updated successfully, but these errors were encountered:
FromLiQg
changed the title
Migrate app-framewrok, app-mgr, and wamr-sdk to a new code repository.
Migrate the code related to app-framewrok to a new code repository.
Jun 30, 2023
Hello to all developers who use WAMR. We decided to migrate the code related to app-framework to an independent repository wamr-app-framework under bytecodealliance.
Before we go into the details, we apologize for any inconvenience this may cause to developers using WAMR. If you are using the app-framework related code for your business, this action may have an impact on your operations.
There are two reasons why we decided to separate the wamr-app-framework from the wamr:
What will be migrated out:
The meeting notes:
https://github.com/bytecodealliance/wasm-micro-runtime/wiki/TSC-meeting-notes.
The new repository:
https://github.com/bytecodealliance/wamr-app-framework
The related PRs:
bytecodealliance/wamr-app-framework#1
#2305
The text was updated successfully, but these errors were encountered: