openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #01646
Re: Feature Freeze status
On Thu, Mar 31, 2011 at 5:21 PM, Michael Barton
<mike-launchpad@xxxxxxxxxxxxxxxx> wrote:
> I'm gonna +1 Todd.
>
> Actually, apache server has a great dev process. They have goals for
> releases, but people are welcome to submit patches to their mailing
> list any time, get comments on them, then they're merged if and when
> people vote them as ready.
We're talking about prioritizing the merge proposals that pile up
based on whether such public discussion has occurred on the ML and/or
has been documented on a blueprint. We're not talking about limiting
people's ability to submit patches. We're talking about prioritizing
the reviews that have been proposed...
-jay
References
-
Feature Freeze status
From: Thierry Carrez, 2011-03-28
-
Re: Feature Freeze status
From: Jay Pipes, 2011-03-28
-
Re: Feature Freeze status
From: Justin Santa Barbara, 2011-03-28
-
Re: Feature Freeze status
From: Jay Pipes, 2011-03-28
-
Re: Feature Freeze status
From: Todd Willey, 2011-03-28
-
Re: Feature Freeze status
From: Jay Pipes, 2011-03-28
-
Re: Feature Freeze status
From: Todd Willey, 2011-03-28
-
Re: Feature Freeze status
From: Ewan Mellor, 2011-03-28
-
Re: Feature Freeze status
From: Todd Willey, 2011-03-29
-
Re: Feature Freeze status
From: Ewan Mellor, 2011-03-29
-
Re: Feature Freeze status
From: Todd Willey, 2011-03-29
-
Re: Feature Freeze status
From: Thierry Carrez, 2011-03-30
-
Re: Feature Freeze status
From: Todd Willey, 2011-03-30
-
Re: Feature Freeze status
From: Jay Pipes, 2011-03-30
-
Re: Feature Freeze status
From: Todd Willey, 2011-03-31
-
Re: Feature Freeze status
From: Jay Pipes, 2011-03-31
-
Re: Feature Freeze status
From: Michael Barton, 2011-03-31