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
When a release of Symphony is made, the symphony-matlab repo is tagged but the symphony-core repo is not. Because of this, there's not a great way to go back and look at the state of the core source code at particular release versions.
If we add the core repo as a submodule to the matlab module, the matlab repo tag will allow us to preserve the revision of the core repo used to make that release. It will also make it easier to automate more of the release process, perhaps with a "release.m" or "deploy.m" script.
The text was updated successfully, but these errors were encountered:
cafarm
changed the title
Move symphony-core into the symphony-matlab repo as a submodule
Add symphony-core to the symphony-matlab repo as a submodule
Sep 30, 2016
When a release of Symphony is made, the symphony-matlab repo is tagged but the symphony-core repo is not. Because of this, there's not a great way to go back and look at the state of the core source code at particular release versions.
If we add the core repo as a submodule to the matlab module, the matlab repo tag will allow us to preserve the revision of the core repo used to make that release. It will also make it easier to automate more of the release process, perhaps with a "release.m" or "deploy.m" script.
The text was updated successfully, but these errors were encountered: