> I was under the impression that idempotent upgrade paths and MySQL
routines had addressed most upgrade challenges. If issues remain, we
should explore technical solutions rather than introduce broad restrictions.
This normally will work for adding things; however, I do not see how
removing a
It seems we're going in circles at this point.
I can't support the proposal to limit DB updates in releases, as it feels
overly restrictive. Users can follow best practices such as taking DB backups
(or snapshots of their mgmt/db instances when virtualised) before upgrading,
which allows for saf
Hello all,
Thanks for expanding the proposal, João.
I believe your proposal embraces a big portion of the processes and use
cases; however, there are some points I think we can improve to make
changes more smoothly to the community and end-users. I will express
them as counterpoints of Rohit'
