Thanks Dongjoon for initiating this. I wanted to include the release policy into this discussion as that will influence what kind of cadence we might need.
I would like to understand the differentiation between a Patch Release X.Y.Z and a Minor Release X.Y. Are there any scenarios where a minor enhancement might be included into a patch release instead of waiting for a minor release? Regards, Pavan > On Oct 16, 2021, at 8:56 PM, Dongjoon Hyun <dongjoon.h...@gmail.com> wrote: > > Hi, All. > > There were some questions and discussion about Apache ORC release cadence > at our GitHub PR. I want to share it with you and get your opinion on it. > > https://github.com/apache/orc/pull/936#issuecomment-944017204 > > According to our release page, Apache ORC release cadence requires > one or two years for the next minor version. > > https://orc.apache.org/docs/releases.html > - 1.4.0: 2017-05-08 > - 1.5.0: 2018-05-14 (About 1 year and 6 days) > - 1.6.0: 2019-09-03 (About 1 year and 4 month) > - 1.7.0: 2021-09-15 (About 2 years and 12 days) > - 1.8.0: 2023-09-15 (About 2 years?) > > Apache ORC release cadence is also related to the EOL of the old releases. > For example, > - 1.5.x was maintained for 40 months and was archived on 2021-09-15. > - 1.6.x EOL is expected on 2022-09-03 if we maintain it for 3 years. > - 1.7.x EOL is expected on 2024-09-15 if we maintain it for 3 years. > > What is your expectation on Apache ORC release cadence? > > Dongjoon
