looo wrote: ↑Mon Aug 26, 2019 7:10 amOk, so the bitbucket repo might switch to git and syncing our repo with upstream will be easier. I guess at one point we can merge everything back into the bitbucket repo, but better wait for this change and also for a new coin release (if this will ever happen).kkremitzki wrote: ↑Sat Aug 24, 2019 4:36 amSince Bitbucket is ending Mercurial support something is going to have to change one way or another.
now they're trying to figure out solutions around that but the thread has gone cold. I bumped it again.The only “issue” I see is that on Bitbucket, issues and pull requests are individually numbered (so both issue #10 and PR #10 can coexist), whilst on Github issues and PRs share the same number sequence (so if the last issue is #10, the next PR is #11). Unfortunately, this causes commit messages for PR merges to be automatically linked to the (wrong) issue, like the last commit on June 13, 2019, on https://github.com/VolkerEnderlein/test ... its/master.
I was literally going to bump this thread today to inquiry about this, because I saw that you made a release.
Nearly all coin related libraries have new releses. There are no big changes but this is great as we now don't have to build against specific commits. This is the main advantage of these releases.
Regarding pyside2 devs pyside2 version should match the qt version. On conda-forge we didn't know about this but 5.14 showed that it won't work without patching with qt5.12. As we already used pyside2 5.13 with qt5.12 we are now patching pyside2 5.13 to work with python3.8 which were the most important changes coming with 5.14. So the combination 5.14 + qt5.12 might work with patching but officially it seems this is not supported anymore.