weizhouapache opened a new pull request, #382:
URL: https://github.com/apache/cloudstack-documentation/pull/382
(no comment)
--
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 comment.
weizhouapache commented on PR #382:
URL:
https://github.com/apache/cloudstack-documentation/pull/382#issuecomment-1938241099
@blueorangutan docbuild
--
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
blueorangutan commented on PR #382:
URL:
https://github.com/apache/cloudstack-documentation/pull/382#issuecomment-1938241764
@weizhouapache a Jenkins job has been kicked to build the document. I'll
keep you posted as I make progress.
--
This is an automated message from the Apache Git Se
blueorangutan commented on PR #382:
URL:
https://github.com/apache/cloudstack-documentation/pull/382#issuecomment-1938243169
QA-Doc build preview: https://qa.cloudstack.cloud/builds/docs-build/pr/382.
(QA-JID 212)
--
This is an automated message from the Apache Git Service.
To respond to
Hi All,
CloudStack 4.19.0.0 is the latest LTS release. There are already some open
issues [1] and pull requests [2] targeted for 4.19.1.0 [3] release.
I'd like to propose and put myself forward as the release manager for 4.19.1.0
if no objections there. Please ping me (@sureshanaparti) on GitH
no worries as João proposed to release 4.18.2 in march, but let's
make sure we have a good period between the two.
On Mon, Feb 12, 2024 at 12:50 PM Suresh Anaparti
wrote:
>
> Hi All,
>
> CloudStack 4.19.0.0 is the latest LTS release. There are already some open
> issues [1] and pull requests [2
Thanks for volunteering Suresh. Agree as Daan has mentioned, community would
benefit to have the 4.18.2.0 first with some gap to then have 4.19.1.0. The
4.19.1 RC by May end or early June LGTM.
Regards.
From: Daan Hoogland
Sent: Monday, February 12, 2024 5:2
bump,
@Daniel Salvador is there any technical reason to keep the 4? any
reason why there must be a 5 instead of a 21, 22 or 23? We are
maintaining 4 number semantic versioning for no reason, as I see it.
On Tue, Jan 30, 2024 at 12:02 PM Daan Hoogland wrote:
>
> Daniel, "technical" reasons for dro
adidiborg commented on PR #77:
URL:
https://github.com/apache/cloudstack-terraform-provider/pull/77#issuecomment-1939069300
Hi @rohityadavcloud, any tentative timelines when v0.5.0 would release?
Already merged features could be of a lot of use 😄
--
This is an automated message from the
rohityadavcloud commented on PR #77:
URL:
https://github.com/apache/cloudstack-terraform-provider/pull/77#issuecomment-1940435831
Hi @adidiborg welcome to the opensource project, I hear you and I hope the
community can work towards a release soon. I hope the next TF release will be
sometim
rohityadavcloud merged PR #374:
URL: https://github.com/apache/cloudstack-documentation/pull/374
--
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 comment.
To unsubscribe, e-mail: dev-uns
Hi,
On main (I think on 4.19 also) there is an issue seen when deploying database
using the command “mvn -Pdeveloper -pl developer -Ddeploydb”
> Processing upgrade: com.cloud.upgrade.DatabaseUpgradeChecker
[WARNING]
java.lang.reflect.InvocationTargetException
at jdk.internal.refl
adidiborg commented on PR #77:
URL:
https://github.com/apache/cloudstack-terraform-provider/pull/77#issuecomment-1940493371
> Hi @adidiborg welcome to the opensource project, I hear you and I hope the
community can work towards a release soon. I hope the next TF release will be
sometime in
13 matches
Mail list logo
