Jones, Bruce E wrote:
[...] Going forward I’d like to figure out how to align with the overall OpenStack release cadence. That topic will be discussed at the September PTG – you can find the draft agenda at https://etherpad.openstack.org/p/stx-PTG-agenda. Please feel free to add any topics you’d like to see discussed there.
I'll try to join on that discussion !
[...] *Proposed schedule*
RC1: August 29th
RC2: September 26th - Feature Freeze
RC3: October 24th - Bug freeze - only absolutely critical bug fixes after this
RC4: November 7th - Final release candidate
If that is something you can change, I'd recommend that you keep the "RC" term for real release candidates -- things that could, at least in theory, be used as final releases. At the very least, RCs should be feature complete. Otherwise if you use them as basic development milestones, you dilute their meaning, which makes it harder to encourage people outside of your core group to actually test them. So I'd recommend using "beta1", "beta2"... for feature-incomplete milestones, and switch to "rc1" once you reach bug freeze :) Regards, -- Thierry Carrez (ttx) OpenStack Release Management team