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
For rendering the notebooks wradlib is installed from the strip1.0.0-branch at the moment.
After switching branches in wradlib (strip1.0.0 -> master) wradlib need to be installed from master branch. In normal operation (render notebooks to devel-branch) nothing is changed.
If we have a wradlib tagged release, we want to create a dedicated tagged branch with rendered notebooks. This can be done by creating a named branch. If the CI runs from a tagged wradlib release, the rendered notebooks will not be pushed to the devel-branch, but to a named branch.
Proposal:
wradlib release tag: 1.0.0 (considering semver)
no special wradlib-notebooks version
wradlib-notebooks render branch: 1.0.0
Following this proposal we just have restart the last master-build to create a new render build. We even might think of automating this, initiating the new Travis-run from wradlib-repo.
The text was updated successfully, but these errors were encountered:
For rendering the notebooks
wradlib
is installed from thestrip1.0.0
-branch at the moment.After switching branches in
wradlib
(strip1.0.0 -> master)wradlib
need to be installed from master branch. Innormal
operation (render notebooks todevel
-branch) nothing is changed.If we have a wradlib tagged release, we want to create a dedicated tagged branch with rendered notebooks. This can be done by creating a named branch. If the CI runs from a tagged wradlib release, the rendered notebooks will not be pushed to the devel-branch, but to a named branch.
Proposal:
wradlib
release tag:1.0.0
(considering semver)wradlib-notebooks
versionwradlib-notebooks
render branch:1.0.0
Following this proposal we just have restart the last master-build to create a new render build. We even might think of automating this, initiating the new Travis-run from wradlib-repo.
The text was updated successfully, but these errors were encountered: