also, as mentioned in the team meeting, we should ...
# development
w
also, as mentioned in the team meeting, we should talk about how to adjust our release strategy to be able to run release candidates more frequently, rather than “weekly”, as is suggested today: https://www.pantsbuild.org/v2.17/docs/release-strategy
👍 1
one way to do that would be to assign a release manager for an entire
x.y.z
cycle… i.e. for all alphas/rcs in
2.16.0
, with a separate release manager for all alphas/rcs in
2.16.1
bump: i think that this would help tighten up the
rc
schedule, to avoid overlapping an
rc
period with the need to cut a new stable branch