2.0.0 release

[ianmkenney]

With #36, the get_propka function is removed. Per the deprecation warning, this means a release of 2.0.0 is needed.

Release checklist

• addressed all issues for 2.0.0 milestone
• updated release (PR v2.0.0 #50 )
• tagged as 2.0.0
• tested package
• created new release on GitHub
• upload to test.pypi.org (create package on test.pypi.org first, add @IAlibay and @orbeckst as admins)
• test the test.pypi package
• upload pypi package

[orbeckst]

See #20 (comment) for decision to release a version that restricts compatibility to earlier version of PROPKA.

[orbeckst]

I added a generic release checklist.

@ianmkenney can you please be in charge to create the package on https://test.pypi.org/ for an initial package test. It's a 2.0.0 so let's get the package right first time and not have to do 2.0.1 on pypi immediately...

@ianmkenney we currently do not have an automated deployment workflow so we need to do test.pypi and pypi manually. @IAlibay, have you repackaged your deployment workflows as actions already?

[IAlibay]

@IAlibay, have you repackaged your deployment workflows as actions already?

Unfortunately it's not finished yet, probably would aim for the 2.1 release. To be honest, as long as it uploads to testpypi we shouldn't have too much trouble with packaging here.

Note: we should try to uplaod wheels too if we can.

[ianmkenney]

@IAlibay @orbeckst what are your test pypi usernames?

[IAlibay]

IAlibay I'm a simple person :P

[orbeckst]

Oliver.Beckstein IIRCAm 2/15/23 um 12:37 schrieb Irfan Alibay ***@***.***>: IAlibay I'm a simple person :P —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>

[ianmkenney]

@orbeckst @IAlibay should be done

[orbeckst]

Then go ahead and close the issue!