On Fri, 6 Feb 2026 at 09:13, Dianjin Wang <[email protected]> wrote: > > Hi Kirill, > > On Thu, Feb 5, 2026 at 11:08 PM Kirill Reshke <[email protected]> wrote: > > > > Sure > > This will in fact resolve many problems, not only CVE > > So, how do we organize this? Do we need big excel as in gpdb > > cherry-pick process? > > > > I think both approaches could work well — a shared Google Sheet or a > GitHub Project/issue tracker. The key is to keep the progress > transparent and make it easy for others to participate and contribute. > > I want to share more ideas on the minior kernel upgrade for the reference. > > Between PG 14.4 and 14.20 there are ~1352 commits, so a phased upgrade > could be a reasonable approach. For example, upgrading incrementally > (14.4 → 14.5 → 14.6, etc. ~100 commits per step) or grouping several > minor versions per step could help keep the process more controlled > and reduce risk. Curious to hear what others think.
I don't have a strong opinion here. But to keep the Cloudberry project more Postgres-y, let's try an incremental approach . > BTW, would you be interested in leading this upgrade effort, if you > have the bandwidth? Having a coordinator would greatly help drive this > forward. I would love to! But I'm a little inexperienced in the GitHub Project/issue tracker. Anyway I can cherry-pick for sure and manage commit statuses/reviewing other people's PRs. > Best, > Dianjin Wang > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > -- Best regards, Kirill Reshke --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
