MAINT: Release?

[pyvista]

MAINT: Release?

[akaszynski]

We've automated releases with azure pipelines, so making a release (should) be as easy as:

git checkout master
git tag <version tag>
git push --tags

Our current tags are 0.1.0 and 0.1.1 and follow semantic versioning. I've neglected the "v", and I've seen repositories use and not use it, so I think it's ok to exclude it.

We can follow pyvista's branching scheme as well if we wish to maintain a minor branch for patch releases for pyvistaqt as well, and maybe that's a good idea so we can rapidly push patch releases when necessary. See CONTRIBUTING.mdfor more details on that.

[larsoner]

Probably need to change https://github.com/pyvista/pyvistaqt/blob/master/pyvistaqt/_version.py#L3, too, right?

[larsoner]

(Okay for me to change _version.py, tag 0.1.2, and push?)

[akaszynski]

Correct, and that's the only place where you need to change the version since that's read into setup.py.

If we're adding features and not just bug fixes, you're good to go to 0.2.0. Adding release notes on the releases page is always a good touch, but not necessary.

[larsoner]

Indeed Azure seems to be having an issue with tags as of today

https://developercommunity.visualstudio.com/content/problem/1157675/tag-triggered-runs-failing-could-not-find-a-servic.html

[GuillaumeFavelier]

+1 for a release. Usually, @akaszynski takes care of it.

[banesullivan]

I'd like to push out a new release of PyVista proper as well

[larsoner]

Argh, tried to push with tags but failed because I need to make a PR -- the protected branch wouldn't let me push the _version.py directly to master. I'll try with a PR and tag force push, but might have to end up tagging + versioning 0.2.1 instead of 0.2.0 because I assumed I could direct push...

[akaszynski]

Argh, tried to push with tags but failed because I need to make a PR -- the protected branch wouldn't let me push the _version.py directly to master. I'll try with a PR and tag force push, but might have to end up tagging + versioning 0.2.1 instead of 0.2.0 because I assumed I could direct push...

That's fine. That's what patches are for. Let me know if you need me to tag it and I'll get it done.

[akaszynski]

I saw the tag. I'll delete it and retag 0.2.0. The pipeline will just redo the release.

[akaszynski]

So much for automated...

I tagged it, but something was messed up on azure/github and the build job failed after deleting and pushing the tags again. I just ended up building the sdist and wheel and pushing that. Master passes, so we're good to go.

0.2.0 is out on https://pypi.org/project/pyvistaqt/

Thanks @larsoner for pushing to get this done. The module needed it (and so does pyvista).