The release process is based on branch juggling from master to milestone-proposed to stable/X. This has interesting consequences on QA, creating a window just before release where (a) you can introduce tempest changes that would break release branches and (b) you can't really have grenade jobs on the development branch. This session will discuss a way out of this maze.
In the remaining time, we'll discuss improvements to the process around global requirements (and the openstack/requirements repository).
