Prerelease 2.0.0

[IAlibay]

Towards 2.0.0

[orbeckst]

lgtm

[orbeckst]

(Technically speaking, merges into master do not require an approval...)

[IAlibay]

Thanks @orbeckst I'm going to squash-merge without waiting for CI given that we're going to run testpypi half a dozen times so merge CI will have come back to shout at us if there's any issues by then.

[orbeckst]

Docs build ... but the introductory parts just need to be chopped to pieces and burned.

[IAlibay]

Docs build ... but the introductory parts just need to be chopped to pieces and burned.

Sorry I didn't catch that, what did you mean?

[orbeckst]

Sorry, was in a hurry when I wrote this. What I meant was: I did not wait for all CI to pass but checked the docs that had already built. These looked good in the sense that version and date were 2.0.0 and today. But then I browsed the docs and was reminded that the initial chapters are just terrible and outdated and we would be better off if they weren’t there and just had a link to the fantastic User Guide. Nothing to be done for the 2.0.0 release but something to be done in the not too distant future.

…

Am 8/21/21 um 10:03 schrieb Irfan Alibay ***@***.***>:  Docs build ... but the introductory parts just need to be chopped to pieces and burned. Sorry I didn't catch that, what did you mean? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.