Next release planning - v0.6.0

[rohityadavcloud]

Discuss via this issue the scope & timeline of the next TF provider release v0.6.0.

Some of the items (issues & PRs) tracked by this milestone are at:
https://github.com/apache/cloudstack-terraform-provider/milestone/3

[rohityadavcloud]

Request for comments - cc @CodeBleu @kiranchavala @vishesh92 @borisstoyanov @fabiomatavelli @poddm and others

[CodeBleu]

the abovve issue that was closed was re-opened as this - #138

[CodeBleu]

Well, we're here... the last month of the 4th Qtr. 😄

Are we still on target to get a release out before end of year? @rohityadavcloud

I personally really need the service offering stuff working and in the next release as soon as possible. 🤞

[rohityadavcloud]

Hi @CodeBleu thanks for the message and I understand your interests. our release plan are on best-efforts basis. Unfortunately 4.20 (GA) took more time than we had anticipated and then we got busy at CCC in last few weeks. We're mostly busy with $dayjob projects, but this is our on roadmap plan and our @kiranchavala is likely going to volunteer as a release manager in Q1 '25.

If you're interested and have patience and time/bandwidth you can help drive a release (in which case you should discuss on our dev@ ML), as a community driven project several users have become committers & release managers. Of course, one can build/use a private build/release, or if you'd prefer we can help kick a pre-rc tag (no promises on timeline though - as it's Dec, many at work and PMCs in the community may have less availability). Hope this makes sense.

[chrxmvtik]

Would be great if you guys could include #147 in the next rc/release, this thing keeps us from automation providing loadbalancer with terraform.

[btzq]

Looking forward to v0.6.0! The existing list of backlogs would help greatly make our lives easier!

[ianc769]

Will this update the provider to support 4.20 of cloudstack? They made some API Changes
I have a pending PR here - #167 and will likey make more in the future to support our use cases.
Rationale: We are creating a private cloud with terraform/cloudstack and some of our use cases require currently missing features.