New release?

[kdolum]

Should we make a new release , maybe when the current run of changes is finished? It would be nice for people using pip and conda to be able to easily get the updated code with bugs fixed.
What about zenodo? I see there that version 1.0 is there with an encouragement for people to cite it in their papers, but that is very old now.

[AaronDJohnson]

I have one more bug to add, and then fix before the next release. We definitely should do a release soon for all the bug fixes though.

[vhaasteren]

About Zenodo: I believe it is possible to link a github project to Zenodo. A new github release should then automatically be updated on Zenodo. It sounds like that is not set up. If we can make that work we should do that

[kdolum]

Are we ready to make a release now? What has to be done?

[vhaasteren]

With the upcoming DR3 analysis, we should definitely do a new release. @AaronDJohnson, do you have any extra bugs/additions? Otherwise we should go ahead

[AaronDJohnson]

The bug that I wanted to fix was the swap acceptance rate output for PTswaps. That is complete, so I'm ready for a release.

[vhaasteren]

Actually, I realize now, the 'acor' package is giving people headaches. We should remove/replace it before releasing anything. I'll make an issue for it.

[kdolum]

Now that #51 was merged are we ready to make a release?