Open jdpleiness opened 7 months ago
Date: 2024-03-19
🟡 At Risk
N/A
This is still on hold due to work on the release process and tracking release items.
Created by jacob.pleiness@sourcegraph.com
Date: 2024-03-28
🟡 At Risk
N/A
This OKR is on hold to make priority for Appliance OKRs and release process work that was added to this cycle.
Created by jacob.pleiness@sourcegraph.com
Date: 2024-04-08
🟡 At Risk
Current: Effectively on hold for the time being
Have ideas for how to move this forward in the near future.
Appliance work is taking priority currently
Created by jacob.pleiness@sourcegraph.com
Date: 2024-04-16
🟡 At Risk
Current: See last entry, status unchanged for now
N/A
See last entry
Created by jacob.pleiness@sourcegraph.com
Date: 2024-04-25
🟡 At Risk
Current: See last entry, status unchanged for now
N/A
See last entry, status unchanged for now
Created by jacob.pleiness@sourcegraph.com
Date: 2024-05-06
🟡 At Risk
Current: Currently working on rolling out a plan to get this started and drive forward the upgrade
N/A
This is going to likely be a long tail processes and will not complete this quarter
Created by jacob.pleiness@sourcegraph.com
Date: 2024-05-20
🟡 At Risk
Current: RFC 952 in progress for this
N/A
This will carry over as it is a long tail process. However it will fit better within the new linear RFC structure/setup
Created by jacob.pleiness@sourcegraph.com
Our current deployments are shipping an old version of Postgres that is near EOL (2024). Newer versions of Postgres offer improved performance and new features. Ensure Sourcegraph is compatible with the latest version of Postgres and migrate our deployments to ship this version.