Hi team, We have started working on the hive-3.2.0 release. The plan is to cut branch-3.2 from the base branch-3. While we were working on the 3.2.0 release, we found that there are some commits (Please refer to this Parent JIRA for the analysis - https://issues.apache.org/jira/browse/HIVE-26752) which went to branch-3.1 which doesn’t exist in the branch-3, same we are planning to backport to branch-3. There can be two approaches
1. Cherry-pick missed commits and push to branch-3 2. Create Jira's for each commit and upload patch. Mostly we feel the second option will be better, any other thoughts will be appreciated. We also need help on creating the pre-commit pipelines for branch-3 as we don’t have Jenkin’s access. Please feel free to add any Jira's which you want to have to 3.2.0. All the changes for the 3.2.0 can be tracked here - Apache Hive - Agile Board - ASF JIRA<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fsecure%2FRapidBoard.jspa%3FrapidView%3D564%26view%3Ddetail%26selectedIssue%3DHIVE-26749%26quickFilter%3D2586&data=05%7C01%7Crajaman%40microsoft.com%7C9c962a68b64741b00b5108dad417bd77%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638055495724889800%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=HjU18Mdtx0Xd8paKPz0Dvr0TF%2FjPCUy5qqJbaB4Wkk0%3D&reserved=0> A friendly request/reminder - After this exercise if any ongoing bug fixes on branch-3.x should also be cherry-picked to the base branch-3 Thanks, Aman.