Re: [PR] Language editting and added info links [cloudstack-documentation]

slavkap commented on PR #386: URL: https://github.com/apache/cloudstack-documentation/pull/386#issuecomment-2634262975 @DaanHoogland, yes, I think it's alright on main -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use t

Re: [PR] Language editting and added info links [cloudstack-documentation]

DaanHoogland commented on PR #386: URL: https://github.com/apache/cloudstack-documentation/pull/386#issuecomment-2634122111 @slavkap , main only? -- 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

Re: [PR] Fix update of VM details [cloudstack-terraform-provider]

CodeBleu commented on PR #158: URL: https://github.com/apache/cloudstack-terraform-provider/pull/158#issuecomment-2634291643 @vishesh92 please see #148 as there are still issues -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHu

Re: [I] Issue with Details in cloudstack_instance resource [cloudstack-terraform-provider]

CodeBleu commented on issue #148: URL: https://github.com/apache/cloudstack-terraform-provider/issues/148#issuecomment-2634288870 @vishesh92 in regards to #158 , I have tested those changes, but still having issues. ![Image](https://github.com/user-attachments/assets/89c08847-1f0c

Re: [VOTE] release candidate 4.19.2.0

Hi Wei, thanks for you answer. About this issue, we do some tests and we think it is a bug. I will give you more details about the tests: We have CloudStack 4.19.1 KVM cluster CS has two physical network interfaces configured in CloudStack as follows:  * *Physical Network 1 (cloudbr0)*: Hand

Re: [VOTE] release candidate 4.19.2.0

Bernardo, First thanks for your feedback. On Mon, Feb 3, 2025 at 7:51 PM Bernardo De Marco Gonçalves < bernardomg2...@gmail.com> wrote: > Hello Daan, all > > I got a little bit confused with the fact that the RC for the 4.19.2.0 > release was opened for voting and, in the meantime, we were still

Re: [PROPOSE] RM for 4.21.0

Thanks Suresh for volunteering, let's review and discuss the timeline again in a couple of weeks time. Regards. From: Daan Hoogland Sent: Monday, February 3, 2025 19:03 To: dev@cloudstack.apache.org ; Suresh Anaparti Cc: users Subject: Re: [PROPOSE] RM f

Re: [VOTE] release candidate 4.19.2.0

Hi Daan, Can we start a different thread cutting a new RC on 4.19.2.0, if those fixes accepted in 4.19 branch (after RC1) must make into 4.19.2.0? Please also specify the RC number on the subject to avoid confusions, thanks. Regards. From: Daan Hoogland S

Re: [PROPOSE] RM for 4.21.0

Hello Suresh, all I'm +1 with you as RM for 4.21. Regarding the schedule, for the project's standards, it is an early release with only 6 months apart from the last minor (our average is around 9 months if I'm not mistaken). However, I'm for it, I believe that a shorter release cycle would be