May I propose we hold the vote, this has three different topics being
considered which looks like still need to be discussed. Also we cannot vote on
some of the things whose details are yet to be completed defined and proposed.
Regards.
From: João Jandre
Sent:
Hello, Rohit
I'm very sorry to hear that your country is at war. Do you think that if
we extend the voting to a full week, you can participate?
Regarding your comments:
1. Semver is very specific on how the version naming should be; it
should only contain three version numbers, not four. Fur
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
blueorangutan commented on PR #488:
URL:
https://github.com/apache/cloudstack-documentation/pull/488#issuecomment-2863753198
QA-Doc build preview: https://qa.cloudstack.cloud/builds/docs-build/pr/488.
(QA-JID 333)
--
This is an automated message from the Apache Git Service.
To respond to
blueorangutan commented on PR #488:
URL:
https://github.com/apache/cloudstack-documentation/pull/488#issuecomment-2863751226
@sureshanaparti 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 S
sureshanaparti commented on PR #488:
URL:
https://github.com/apache/cloudstack-documentation/pull/488#issuecomment-2863747549
@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
Sorry all - I'm busy at work but want to chime in after considering the thread
(plus my country's at war atm). I need more time and I wouldn't be able to vote
within 72 hrs.
On the face value - none of the three things needs voting on, we already use
the semver & have used deprecation process f
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
