i think the current CI is not broken due to bugs or regressions but rather just some unexpected tooling upgrades due to newer versions. i'm not seeing huge risk for branching.
on the other hand, i've been wishing to fix it (in both rust lib and java lib) but haven't got enough time to get it done properly. if branching makes it easier to have a master "slightly broken" being acceptable, then i can maybe merge both rust and java fixes sequentially. that'll be one benefit. On July 28, 2022, Jens Geyer <je...@apache.org> wrote: > @all, > > the plan was to create a 0.17.0 branch this week to have it ready in > August or September for the next release. However, given the current > state of CI I'm not quite sure if I should start this at all. > > Opinions? Prepare 0.17.0 release branch yes or no? > > Have fun, > JensG
