Predictable release cycle

[pinepain]

First of all, thank you for all hard work has been done!

I'd like to clarify the state and plans of release frequency to improve visibility on this question. Currently there are some features, like #152 which was merged on Oct 4, it's 5 month ago. Current release, 1.1.1 was tagged on Sept 29, so we close to hit 6 month with it, which is half a year. I understand that you are busy there and this is an open-source that's why I'd suggest to improve release cycle to be predictable and then adhere to it.

While DigitalOcean plays important role in the modern era of cloud providers, it's hard to deny that this is a must to have. And that having an API for new feature to be propagated to the library for 5 month is not something that should lasts longer.

From $$$ perspective it's hard to sell business moving to DO partially because they see that there is a lot of place for improvements which ended up loosing a clients whose monthly budget varies from few $k to few $10k (they go to AWS if you would ask). For that money tagging releases with new DO features propageted to the tools should be a good choice in terms of ROI, right?

I really like DO and I'm a bit frustrated to see this gap in tooling is even increasing for that past few years. I'm pretty sure you are working on even better and exciting features, but please, do a bit more towards tooling around DigitalOcean.

Thank you for reading!

[mauricio]

Hey @pinepain, that's true, we need to do better at releases, will keep this in mind whenever we get stuff in here, thanks for the feedback!

[pinepain]

Thanks for tagging v1.1.2 release!