> > I think the burden of maintaining a release branch is not just > backporting. We need to run CI to make sure every maintained release branch > are working, and do testing for that. It's a burden if there are too many > release branches. > > That's a good point, we do need to run CI on all supported versions. However, I think that updates to the release branches are not nearly as frequent as updates to master branch. So, I think it might actually be reasonable to run CI on ~10 release branches, since we will only need to run it when bug fixes get backported.
- Release policy and 1.6 release schedule Greg Mann
- Re: Release policy and 1.6 release schedule Zhitao Li
- Re: Release policy and 1.6 release schedule Jie Yu
- Re: Release policy and 1.6 release schedule Greg Mann
- Re: Release policy and 1.6 release schedul... Jie Yu
- Re: Release policy and 1.6 release sc... Jie Yu
- Re: Release policy and 1.6 releas... Greg Mann
- Re: Release policy and 1.6 release sc... Vinod Kone
- Re: Release policy and 1.6 releas... Alex Rukletsov
- Re: Release policy and 1.6 re... Greg Mann
- Re: Release policy and 1.6 re... Greg Mann
- Re: Release policy and 1.6 re... Greg Mann
