New release (v1.1)

[RaulPPelaez]

#106 has been merged, and some other functionalities are not released yet (e.g #101, #97 ,...)
Maybe its time for a new release?
cc @peastman @raimis

[sef43]

A minor related issue is that the versions on conda-forge (latest version is 1.0) do not match the released version numbers on this github repo

[RaulPPelaez]

I see it went from 0.8 to 1.
Current recipe points to 994f92f
Perhaps the sensible thing is to tag that commit with v1.0 and release another tag with the latest commit called v1.1 or something like that?

[raimis]

@peastman why there is a release on conda-forge (conda-forge/openmm-torch-feedstock#33) without tagging in the repo?

[peastman]

Just an oversight, I think. We should create a corresponding release on this repo.

The jump to 1.0 indicated that this package was no longer experimental and all future releases would work to maintain backward compatibility.

[raimis]

OK! I'll create the 1.0 release retrospectively and proceed with 1.1.

[raimis]

1.0 is done: https://github.com/openmm/openmm-torch/releases/tag/v1.0

[raimis]

1.1 is done: https://github.com/openmm/openmm-torch/releases/tag/v1.1

[raimis]

I'll try to build the packages

[raimis]

conda-forge/openmm-torch-feedstock#36

[raimis]

OpenMM-Torch 1.1 is out (https://github.com/openmm/openmm-torch/releases/tag/v1.1, https://anaconda.org/conda-forge/openmm-torch/files?version=1.1)

@jchodera could you make a tweet?

[RaulPPelaez]

Closign this as completed