chore: release 1.16.0

[release-please]

🤖 I have created a release *beep* *boop*

1.16.0 (2020-10-27)

Features

• pass 'client_options' to super ctor (#61) (c4387b3), closes #55

Bug Fixes

• add default filter settings to list_entries (#73) (0a1dd94)
• failing CI tests (#70) (96adeed)

---

This PR was generated with Release Please.

[busunkim96]

@daniel-sanche Merging this will release the library

[daniel-sanche]

@daniel-sanche Merging this will release the library

Do you think it makes sense to make a release soon? Or should we wait until the microgenerator changes are in and do a major release then?

[simonz130]

@daniel-sanche Merging this will release the library

Do you think it makes sense to make a release soon? Or should we wait until the microgenerator changes are in and do a major release then?

If it's a minor version update, we should aim for frequent releases over accumulating content and sparse releases.

[daniel-sanche]

Some of my recent changes are incompatible with Python 2, which should count as a breaking change. And there are a lot more coming soon with changes around microgenerator update. I was thinking we should aim for one big major release after the microgenerator update, and then get back into a regular cadence of smaller releases. What do you think?

[busunkim96]

Ah I didn't realize there were changes that dropped Python 2 support. If that's the case it is probably better to wait.

After that point I'd advocate for frequent releases. It's easier to figure out what the root cause of any bugs are, and rollbacks are less disruptive.

[daniel-sanche]

FWIW It should be pretty easy to bring back Python 2 support if we decide another minor release is worthwhile. But yeah, I think a major release soon and then smaller ones after makes sense