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.
kmuehlbauer
commented
6 years ago
For rendering the notebooks
wradlibis installed from thestrip1.0.0-branch at the moment.After switching branches in
wradlib(strip1.0.0 -> master)wradlibneed to be installed from master branch. Innormaloperation (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:
wradlibrelease tag:1.0.0(considering semver)wradlib-notebooksversionwradlib-notebooksrender branch:1.0.0Following 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.