Hi everyone,
I am pleased to share that the CloudStack European User Group (CSEUG) 2025 is
official! This year's user group will be taking place in Vienna, Austria on May
8th, with the venue TBC.
Registration and the Call for Presentations is open. Please read the event
announcement blog to ac
Thanks, Pearl!
On 2025-01-27 14:14, Pearl Dsilva wrote:
Hi All,
Since we are so close to releasing 4.19.2, and I have been working
closely
with Daan on this release, I thought I could take on the release of
4.20.1.
Hence, I would like to take this opportunity to propose myself for
managing
Thanks for volunteering Pearl,
Rest assured I will be assisting you as much as I can.
On Mon, Jan 27, 2025 at 3:15 PM Pearl Dsilva wrote:
> Hi All,
>
> Since we are so close to releasing 4.19.2, and I have been working closely
> with Daan on this release, I thought I could take on the release of
Hi All,
Since we are so close to releasing 4.19.2, and I have been working closely
with Daan on this release, I thought I could take on the release of 4.20.1.
Hence, I would like to take this opportunity to propose myself for managing
the release of 4.20.1.
Please let me know if there are any obje
Chi/Tata, there are different answers possible.
I will not try to give you a project standpoint on this.
As a company we usually recommend the latest dot release (i.e. not a .0 but a
.1/.2/.1.3 etc.) but also in the end make sure you test the subset of
functionality you will be using / exposing
Can you tell us. Which release should be used for production ??
I was trying hardly the 4.20 and maybe that is the main problem in my case?
Tata Y
> On Jan 27, 2025, at 8:01 AM, Daan Hoogland wrote:
>
> yes Ricardo, All fixes will be merged forward to the 4.20 and main
> branches, provided th
yes Ricardo, All fixes will be merged forward to the 4.20 and main
branches, provided these are still relevant.
On Mon, Jan 27, 2025 at 1:51 PM Ricardo Pertuz
wrote:
> Out of curiosity, are these fixes included/merge in the following 4.20.x
> release?
>
>
> Atte,
>
> Ricardo Pertuz
>
>
> On 27 J
Out of curiosity, are these fixes included/merge in the following 4.20.x
release?
Atte,
Ricardo Pertuz
On 27 Jan 2025 at 6:58 AM -0500, Rohit Yadav , wrote:
> Hi Daan,
>
> Since we're already ready, why don't we cut RC1 sooner that way more people
> can test and if there any blocker/critical
We can definitely do that, yes. If no objections will start on a first RC
tomorrow.
On Mon, Jan 27, 2025 at 12:57 PM Rohit Yadav
wrote:
> Hi Daan,
>
> Since we're already ready, why don't we cut RC1 sooner that way more
> people can test and if there any blocker/critical issues we can still cut
Hi Daan,
Since we're already ready, why don't we cut RC1 sooner that way more people can
test and if there any blocker/critical issues we can still cut another RC?
>From what I've followed, the 4.19 branch has already 100s of issues/PRs fixed
>and ready to create ship a release out of.
Regard
LS,
As stated in [1] I want to call a freeze on the 4.19 branch this week. My
plan is still to create an RC by friday
the current state is ,
- 125 closed PRs -
https://github.com/apache/cloudstack/pulls?q=is%3Apr+milestone%3A4.19.2+is%3Aclosed
- 39 open PRs and -
https://github.com/apache/clouds
11 matches
Mail list logo
