Hello Daan, all
We have already brought this discussion back and forth between different
media (ML->Github Discussions->ML) and from the feedback we got from the
community, I believe that the discussion should stay on the ML, where
the final vote will be held ("If it didn't happen on the maili
The Apache CloudStack project announces the release of LTS security releases
4.18.2.5 and 4.19.1.3 that address CVE-2024-50386 (severity 'Important').
The CVE is explained below.
## CVE-2024-50386: Directly downloaded templates can be used to abuse
KVM-based
infrastructure
Account users in Apa
The Apache CloudStack project announces the release of LTS security releases
4.18.2.4 and 4.19.1.2 that address the following security issues:
- CVE-2024-45219 (severity 'Important')
- CVE-2024-45461 (severity 'Moderate')
- CVE-2024-45462 (severity 'Moderate')
- CVE-2024-45693 (severity 'Importan
The Apache CloudStack project announces the release of LTS security releases
4.18.2.4 and 4.19.1.2 that address the following security issues:
- CVE-2024-45219 (severity 'Important')
- CVE-2024-45461 (severity 'Moderate')
- CVE-2024-45462 (severity 'Moderate')
- CVE-2024-45693 (severity 'Importan
On Fri, 12 Apr 2024 at 1:01 AM Ivet Petrova
wrote:
Hey Daniel,
Great initiative! Hope more people will submit proposals. I think we
posted on socials for the event at some point. Will post today also.
Best regards,
On 12 Apr 2024, at 3:36, Guto Veronezi wrote:
Hello guys,
The Commu
Hello guys,
The Community Over Code North America (COCNA) will happen in October
2024 in Denver. The Call For Tracks for this conference occurred between
December 2023 and January 2024; however, we (the community) did not
engage in the discussion at that time and ended up not having a track
f
Thanks Rohit for your work and thank you guys for the support. I'll put
in my best effort in the role.
Best regards,
Daniel Salvador (gutoveronezi)
On 3/22/24 05:25, Sven Vogel wrote:
Thanks Rohit for your work. As always good.
Congratulations Daniel.
Cheers
Sven
--
On March 22, 20
By agreeing to drop the "4" I think we're effectively voting and agreeing that
we'll not be breaking APIs.
That is not what was discussed in the thread [1]. If we agree that we
will not break APIs, I am -1 on dropping the "4". We need to create a
protocol along with the proposal, otherwise, we
- tell users the old APIs will be removed in version Y, please use new APIs
instead.
- in version Y, remove the old APIs.
This can be done in each major/minor release. No need to wait for 5.0.
-Wei
On Fri, 26 Jan 2024 at 18:51, Guto Veronezi wrote:
Exactly, so you understand now why we must
Hello guys
We finally merged PR #7131 [1]. With that, other PRs targeted to the
branch "main" might get the conflict status. The PR #7131 [1]
description contains instructions on how to fix the conflicts; however,
if you have any doubts, do not hesitate to contact us. For those who
have PRs t
look around, most OS/software do not follow it. iOS/Android?
Ubuntu/Debian/RHEL/Windows ? or Chrome/Firefox ? or kvm/vmware/xenserver ?
By the way, the article is incorrect. Softwares must keep backward
compatibility as much as possible.
-Wei
On Fri, 26 Jan 2024 at 17:32, Guto Veronezi wrote
useless at all.
Kind regards,
Wei
On Thu, 25 Jan 2024 at 15:52, Guto Veronezi wrote:
Hello guys,
It is nice that we are discussing this topic; however, what is the
point? Is it just a semantic change? Or we will be able to introduce
changes that cause incompatibility between versions (alt
Hello guys,
I just replied the discussion thread and I would like to discuss it a
little bit further before voting.
Best regards,
Daniel Salvador (gutoveronezi)
On 1/25/24 11:47, Daan Hoogland wrote:
LS,
As previously discussed [1] there is a growing wish to no longer carry
the version numb
Hello guys,
It is nice that we are discussing this topic; however, what is the
point? Is it just a semantic change? Or we will be able to introduce
changes that cause incompatibility between versions (although some
incompatibilities are already introduced even when they should not)? By
the wa
Hi Ivet,
The proposal seems very promising; looking forward to it.
Best regard,
Daniel Salvador (gutoveronezi)
On 9/19/23 06:59, Ivet Petrova wrote:
Hi all,
Thanks for the good feedback and positive words.
I would suggest that if no-one has something against the new design, we start a
develo
Hello guys,
I think Rohit meant to upgrade the Node version to v18, as NPM is only
the package manager and its latest release is 10.0.
Currently, we do not enforce either Node or NPM version in the building;
therefore, one can use newer Node versions rather than v14. The problem
faced by Roh
16 matches
Mail list logo
