Open Stack

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hey all,

I'm in the middle of brushing up my understanding of how stable
releases work in openstack. It seems we support two releases at the
same time - Havana and Icehouse.

For Icehouse, everything is clear - it gets all appropriate bug fixes,
including performance improvements, security fixes, failure modes etc.

For Havana, it's not that clear. As per [1], Havana is now in
'Security-supported' mode which is somehow different from 'Current
stable release, security-supported' that is Icehouse. My understanding
is that it means that only security fixes are allowed to go into the
branch now. While we still see other types of patches being merged in
stable branches. Those include performance improvements, adoptions to
new third-party software, and other nice-to-have patches. My
suggestion would be to allow only the following types of patches to
old stable branches:

- - security fixes;
- - adoptions that fix major breaks with new versions of third-party
software we depend on.

So, what's our take on that? Is there any difference in how we
consider patches for inclusion between multiple stable branches?

Another thing that is not clear to me is who defines that transition
between general stable branch state into 'Security-supported' one. Are
there any written rules for that, like binding such transition to
trunk milestones?

Alternatively, am I putting too much in that distinction, and all
kinds of stable branch appropriate patches belong to both of the branches?

[1]: https://wiki.openstack.org/wiki/Releases

Cheers,
/Ihar
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBCgAGBQJTyQHbAAoJEC5aWaUY1u57La4IAMZvMzmMS4ajIWk78t0zR7O7
E/m08mP4pi9PZeuBpz1OUWagcr20Z04KabToPkunsrydeEBJsg/0+3PeZvC8Ndio
Io9bJqpCdRsFPS0RN+JW8ad7mf1e1xENYpV1MWlJIq6VfZJdzshZE7ohmuDj3Qzo
kUbqUJYQ4rH9NtXt6qGILNNjsUXByIeI8mfCYqqLxf0j8Al1RlYLeLo5yAn7Cf7S
KF97qKx708nFYmaWMVDw5C1Vq6jgcLAL4BeKUVnDNaG6K5zqLfpzuu+9dqMY83HN
KDUYgaR3fJSglbDfq++hr03tnUQUHo8YWxicztoeUQFx0P/RrKXd4NvbgNMw2uY=
=xwVW
-----END PGP SIGNATURE-----