We cannot publish Data-platform-charm-revision=288 into track latest as we do not provide in-place upgrade from legacy charm to our/new one (juju refresh will corrupt postgresql data on on already installed servers).
The latest track revision=290 is coming for IS team legacy charm. They cannot migrate on 14/stable until we provide extensions support.
So, IS team is still using (and publishing) their charm to the latest/stable, but Mark/Jon do not want to keep it default. They insist to use new data-platform charm by default (14/stable).
Technically we can close latest/stable today as:
- juju deploy --channel latest/stable # will continue working
- charmcraft upload postgresql --channel latest/stable --release # will continue working and will reopen the channel on each release, so we will have to close it again and again.
I hope it is still possible to switch defaults without closing latest/stable. cc: @mthaddon