[Openstack-operators] Fwd: [openstack-dev] [stable] Organizational changes to support stable branches
Roland Chan
roland at aptira.com
Fri Nov 14 09:08:25 UTC 2014
Hi Tom
Re the first 6 months of backporting: "should" would be better than
"may" and "will" would be best. "may' sets an expectation that looks a
lot like a shrug. It's fine as a lower bound on backporting behaviour,
but as an expectation setter it's pretty weak.
--
Roland Chan
Aptira
On 14 November 2014 19:00, Tom Fifield <tom at openstack.org> wrote:
> Hi Ops,
>
> Please see below excerpt from developer ML email regarding changes to
> stable branches. I think this is going to make life better :) Thanks to
> those of you who participated in the discussions at the summit.
>
> The stable team always needs help, so if you're interested in finding
> out more, you can read the full thread at
> http://osdir.com/ml/openstack-dev/2014-11/msg00686.html .
>
>
> Regards,
>
>
> Tom
>
>
> -------- Forwarded Message --------
> Subject: [openstack-dev] [stable] Organizational changes to support
> stable branches
> Date: Thu, 13 Nov 2014 12:34:08 +0100
> From: Thierry Carrez <thierry at openstack.org>
> To: OpenStack Development Mailing List <openstack-dev at lists.openstack.org>
>
> ...
>
> 5. To set expectations right and evolve the meaning of "stable" over
> time to gradually mean more "not changing", we propose to introduce
> support phases for stable branches. During the first 6 months of life of
> a stable branch (Phase I) any significant bug may be backported. During
> the next 6 months of life of a stable branch (Phase II), only critical
> issues and security fixes may be backported. After that and until end of
> life (Phase III), only security fixes may be backported. That way, at
> any given time, there is only one stable branch in "Phase I" support.
>
> 6. In order to raise awareness, all stable branch discussions will now
> happen on the -dev list (with prefix [stable]). The
> openstack-stable-maint list is now only used for periodic jobs reports,
> and is otherwise read-only.
>
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
More information about the OpenStack-operators
mailing list