👍 On Mon, Oct 27, 2025 at 8:05 AM Mick <[email protected]> wrote:
> > > Do we want to re-roll the 5.0.6 release or that can just go out with > 5.0.7? > > > As Stefan says, it will get looked after. > > The practice is to let new commits keep coming into 5.0.6 (jira and > CHANGES) until the vote passes. > It is the release manager's job to create the new jira version and bump > the build.xml. Part of that is moving CHANGES lines into the new version, > and when closing the 5.0.6 version in jira bumping those same jiras to 5.0.7 > > Having done both approaches, this is IMHO the much easier approach. The > moving issues back when a release vote fails is a pita (and more > error-prone), taking into account frequency with whether votes pass or > fail. Also… this incentivises failing a vote and re-cutting, which should > always be "the right thing", and also gives the opportunity to catch rogue > jira tickets (which there often are). > > It's not wide-spread knowledge/reasoning, so appreciate the question :D
