Closed ChristophWWagner closed 1 year ago
Update: testing of master
branch and pull requests is successfully migrated and the test coverage is extended to python 3.9, 3.10, 3.11 and the legay 2.7. Seems to work.
Next step: deployment. Following are my thoughts on this using some semi-manual process. Please comment (@SebastianSemper ?).
master
to stable
. Probably it's not even necessary to restrict the branch from which to merge, since only a few people can merge to stable
, so using some intermediate branch could be fine (suggestion: release-candidate-$(VERSION)
).master
or stable
).stable
) will also perform uploading. If it is possible to reuse the build artifacts from the previous PR run, that could help.Sounds good. I think many OSS project operate like this.
Regarding deployment, I am wondering if it is really necessary to upload packages automatically using CI, since releases are rare enough and our wheels are very generic. We could also simply put some mimic in the makefile and execute this after releases to stable.
d0ne.
Seems that travis-ci.org is deprecated and should be migrated to the service under TLD .com