reshke commented on PR #1574: URL: https://github.com/apache/cloudberry/pull/1574#issuecomment-4028976300
> I have a thought about the cherry-pick strategy for `REL_2_STABLE`. > > Instead of picking individual commits, would it make sense to start from the commits after the previous cherry-pick PR (#1547) and move forward from there? > > My concern is that selecting commits piecemeal might make it harder to manage in the next release cycle, since more commits will be added in between and it may become less clear which ones were already backported. > > If this approach makes sense, we could also keep this PR and use it as the cherry-pick PR for the next release. Hi! I did not get your idea... As of today, the last agreement we met in Apache Cloudberry dev list was [0], which is: ``` PG 14.4 → 14.20 → REL_2_STABLE directly CVE-only fixes → main (already mostly done) Keep main clean for PG16 upgrade ``` So, after this PR there will be no contribution to main branch which is 14.4-14.20 range, so nothing to back-patch. Kernel upgrade will continue in REL_2_STABLE only, tracked here[1]. If I am mistaken is something please clarify .... [0] https://lists.apache.org/thread/bkrx7470kk08kvz2t7rv68gll1sp67vm [1] https://docs.google.com/spreadsheets/d/1vjjEb39QPyXO-nDJZ0tHAtReIQKka0S2YnD2r1AFhkk -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
