s still in play.
Regards.
From: João Jandre
Sent: Thursday, May 15, 2025 00:55
To: dev@cloudstack.apache.org
Subject: Re: [VOTE] Versioning process
Hi, Rohit
In your previous message in this thread you proposed a hold on the vote.
In my reply I said that it would be closed since there was m
s still in play.
Regards.
From: João Jandre
Sent: Thursday, May 15, 2025 00:55
To: dev@cloudstack.apache.org
Subject: Re: [VOTE] Versioning process
Hi, Rohit
In your previous message in this thread you proposed a hold on the vote.
In my reply I said that it would be cl
et to be completed defined and
proposed.
Regards.
From: João Jandre
Sent: Friday, May 9, 2025 12:21:22 AM
To: dev@cloudstack.apache.org
Subject: Re: [VOTE] Versioning process
Hi Daan,
Regarding your first point, adding default values to the DB is different
from ch
the community’s
long-term benefit.
PS. I’ll try to revisit versioning and release policies in light of Joao's
intent in the coming weeks.
Best regards.
From: João Jandre
Sent: Saturday, May 10, 2025 16:42
To: dev@cloudstack.apache.org
Subject:
>
> We should evaluate proposals based on whether they serve the community’s
> long-term benefit.
>
> PS. I’ll try to revisit versioning and release policies in light of Joao's
> intent in the coming weeks.
>
> Best regards.
>
> ________________
> F
er they serve the community’s
long-term benefit.
PS. I’ll try to revisit versioning and release policies in light of Joao's
intent in the coming weeks.
Best regards.
From: João Jandre
Sent: Saturday, May 10, 2025 16:42
To: dev@cloudstack.apache.org
Subj
gards.
From: João Jandre
Sent: Friday, May 9, 2025 12:21:22 AM
To: dev@cloudstack.apache.org
Subject: Re: [VOTE] Versioning process
Hi Daan,
Regarding your first point, adding default values to the DB is different
from changing the DB schema. Changing the DB s
: Friday, May 9, 2025 12:21:22 AM
To: dev@cloudstack.apache.org
Subject: Re: [VOTE] Versioning process
Hi Daan,
Regarding your first point, adding default values to the DB is different
from changing the DB schema. Changing the DB schema would be
creating/removing tables or creating/removing
Hi Daan,
Regarding your first point, adding default values to the DB is different
from changing the DB schema. Changing the DB schema would be
creating/removing tables or creating/removing columns. Thus, adding new
values to tables would not be an issue. Would you like me to add this
definiti
João,
I am completely +1 on item 3.
I am missing the exceptions that we need on both other issues.
- for DB we add hypervisor types in minor versions and those need DB changes
- for both DB and API changes we make exceptions for security releases
given a rewording to include those, I would be compl
10 matches
Mail list logo
