Release PyKE v3.0.0 about pyke

[barentsen]

I restructured the sphinx docs over the weekend to make them clear ahead of the 3.0 release. I pushed this straight to master because it'll be easier to fine-tune using separate PRs. Please review! One thing missing is a "contributing" page.

Finally, we need to update the kepler science website to reflect v3.0. When that's done, we should be good to move from beta to a full release!

[barentsen]

3.0.0 was released last week, congratulations everyone!

[mirca]

+1 for pyke-kepler or even pyke3.

[barentsen]

I think pyketools or pyke3 may be the answer, because pyke-kepler gives the impression that it's not relevant for TESS. I slightly favour pyketools to distinguish it from the existing pyke package on pypi (which we have nothing to do with).

[mirca]

I like pyketools

[barentsen]

Tutorials have been added, so I released version 3.0.beta1 on pip today. Procedure used:

python setup.py sdist
twine upload dist/pyketools-3.0b1.tar.gz

Next, I am going to do a bit more work reviewing the docs and testing tools before releasing 3.0.0.

[barentsen]

I think we are good to release 3.0! The only thing stopping me is #64, because it's a significant change to the API, but I think we can implement this today?

(Resolving parts of #63 would be nice too, but not essential.)

[mirca]

Yeah, #64 and #63 can be done today

[barentsen]

I have bumped the version to 3.0beta4 and pushed a new version to pypi.

I am thinking to release a new version at least every week for the foreseeable future, so that the version on pypi benefits from the various bugfixes that are being made on an almost daily basis now. I propose to switch from beta to 3.0.0 at the occasion of our next big mailing list update, in ~14 days from now, which gives us a reason to include PyKE again in the mailing list update =)

@mirca What do you think of this strategy?

[mirca]

Sounds great, @barentsen!