On Wed, Mar 28, 2018 at 03:34:32PM +0100, Graham Hayes wrote:
> It is more complex than just "joining that team" if the project follows
> stable policy. the stable team have to approve the additions, and do
> reject people trying to join them.
This is true but when we (I) say no I explain what's
On 26/03/2018 14:33, Thierry Carrez wrote:
> Hi!
>
> TL;DR:
> We used to do complex things with ACLs for stable/* branches around
> releases. Let's stop doing that as it's not really useful anyway, and
> just trust the $project-stable-maint teams to do the right thing.
>
>
> Current
On Wed, Mar 28, 2018 at 09:51:34AM -0400, Doug Hellmann wrote:
> Excerpts from Thierry Carrez's message of 2018-03-26 15:33:03 +0200:
> > Hi!
> >
> > TL;DR:
> > We used to do complex things with ACLs for stable/* branches around
> > releases. Let's stop doing that as it's not really useful
Excerpts from Thierry Carrez's message of 2018-03-26 15:33:03 +0200:
> Hi!
>
> TL;DR:
> We used to do complex things with ACLs for stable/* branches around
> releases. Let's stop doing that as it's not really useful anyway, and
> just trust the $project-stable-maint teams to do the right thing.
LGTM
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
On Mon, Mar 26, 2018 at 03:33:03PM +0200, Thierry Carrez wrote:
> Let me know if you have any comment, otherwise we'll start using that
> new process for the Rocky cycle (stable/rocky branch).
Sounds good to me, Thanks Thierry
Yours Tony.
signature.asc
Description: PGP signature
Hi!
TL;DR:
We used to do complex things with ACLs for stable/* branches around
releases. Let's stop doing that as it's not really useful anyway, and
just trust the $project-stable-maint teams to do the right thing.
Current situation:
As we get close to the end of a release cycle, we start
