[MIR] postgresql-14
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
postgresql-14 (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
postgresql-common (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
TL;DR:
We are in the process of clarifying if the dependencies really will be ready to move to PG-14.
If yes => promote PG-14, demote/remove PG-13
If no => remove PG-14
--- Details ---
postgresql-14 now shows up in Jammy component mismatches.
https:/
That is due to postgresql-common being auto-synced and changing the default to PG14.
Conceptually this is the same as
- https:/
- https:/
and all the others before it.
It seems we can go PG-13 in 21.04 as it looks rather good on the main PG-13 transition. Yet there are still a bunch of blockers left:
https:/
I guess those dependencies will need some time and then 4-8 weeks to get everything in shape.
Until then this will probably clutter update-excuses, therefore I'm tagging this as such to be known.
But for expectation, last time a few took quite a while and some even got removed for a short while.
Open issues are tracked here (thanks to Devrim / Myon for the great work)
https:/
Hopefully then eventually (probably ~January) we re-evaluate this and remove PG-13.
Due to the above this is filed as MIR bug so that one looking at mismatches can find it, but not meant to be promoted yet until the to-dos mentioned are resolved - therefore keeping it "invalid" for now..
tags: | added: update-excuse |
Changed in postgresql-common (Ubuntu): | |
status: | New → Incomplete |
tags: | added: server-next |
Changed in postgresql-common (Ubuntu): | |
status: | New → Invalid |
Changed in postgresql-14 (Ubuntu): | |
assignee: | nobody → Lukas Märdian (slyon) |
tags: |
added: server-todo removed: server-next |
Changed in postgresql-common (Ubuntu): | |
status: | Invalid → In Progress |
Changed in sqlalchemy-i18n (Ubuntu): | |
status: | Confirmed → In Progress |
I think we can do the MIR processing on this now, even though the transition itself might still take a while for the last dependencies to be ready. Therefore setting state back to NEW.
I'd assume that this is a "yes, just as before but please ensure that PG-13 is removed before end of cycle". But then I do not want to sign-off my own MIRs and need to wait for a second pair of eyes.