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
definition to the vote?
Regarding the second point, I will add a exception for APIs. Regarding
DB changes I have already specified it in the original voting message.
Best regards,
João Jandre
On 5/8/25 09:47, Daan Hoogland wrote:
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 completely +1 on your proposal.
so for now -0.666...
I would still push back on incompatible changes on major releases btw.
I want users to be able to continue using ACS for all eternity ;) But
we can handle those with migration paths and those would become
regular discussions here at dev@.
On Wed, May 7, 2025 at 7:15 PM João Jandre <j...@apache.org> wrote:
Hello, all
I am starting this voting thread regarding the discussions made in
https://lists.apache.org/thread/4jk31krsjl8cbp5n8wbt7ypwl65g364j. To be
specific, these are the changes that we are going to vote on to follow
during our release process:
1. API Changes: Any changes to APIs that break backwards compatibility
should only be made in MAJOR versions. Currently, these would be our
5.x.x, 6.x.x, etc.. After this thread is finished, I will start another
thread regarding our version naming.
2. Database Schema: Changes to the database schema should be introduced
only in major versions. The only exception is for potential security
changes that require database changes; we never had such cases, and when
(if) it appears, we will properly communicate it to operators/users of ACS.
3. Feature Removal: Update the process of feature removal (see
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=68720798)
to ensure that features are only removed in major versions, after having
been announced at least 6 months in advance in a previous version.
Vote will be open for 72 hours.
For sanity in tallying the vote, can PMC members please be sure to
indicate "(binding)" with their vote?
[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)
