kohrar commented on issue #32:
URL:
https://github.com/apache/cloudstack-terraform-provider/issues/32#issuecomment-1986514645
> @kohrar
>
> I am not hitting the issue on the latest build.
>
> Let me know if i can close the issue
>
>
kohrar commented on issue #32:
URL:
https://github.com/apache/cloudstack-terraform-provider/issues/32#issuecomment-1986505805
Hi @kiranchavala. Thanks for picking up this project.
I gave this provider a try on Apache CloudStack 4.18.1 but seem to have some
issues. I compiled the
agree.
Moreover, we should try to avoid the new upgrade path for 4.xx.2 release.
-Wei
On Friday, March 8, 2024, Rohit Yadav wrote:
> I think it would be most likely that we work towards releasing 4.19.1
> before 4.20.0. Then, it would be sensible to have 4.19.0 -> 4.19.1 ->
> 4.20.0 upgrade
rohityadavcloud commented on PR #78:
URL: https://github.com/apache/cloudstack-go/pull/78#issuecomment-1985353470
ping @shwstppr @vishesh92 can you review and advise on this PR, thanks.
@sbrueseke has advised me privately that they need this for some use with the
cloudstack packer plugin.
I think it would be most likely that we work towards releasing 4.19.1 before
4.20.0. Then, it would be sensible to have 4.19.0 -> 4.19.1 -> 4.20.0 upgrade
path.
Regards.
From: Daan Hoogland
Sent: Friday, March 8, 2024 14:50
To: dev
Subject: [PROPOSE]
devs,
currently we have an upgrade path for 4.19.0.0 to 4.19.1.0 in the 4.19 branch
in the main branch we have a 4.19.0.0 to (4.)20.0.0 upgrade path
merging fails because of this and allowing either or both in main will
cause main to fail (at least after upgrading)
If we are sure that 4.19.1 will
rohityadavcloud commented on issue #86:
URL:
https://github.com/apache/cloudstack-terraform-provider/issues/86#issuecomment-1985230842
Thanks @kiranchavala @vishesh92 looks like we've done a lot this week, I'm
closing on the basis that Kiran has volunteered to serve as the release manager
rohityadavcloud closed issue #86: Plan Next 0.5.0 Interim Release
URL: https://github.com/apache/cloudstack-terraform-provider/issues/86
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific
