Mailing-List: contact general-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@incubator.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CA+ULb+v9cSAZs3Frsu8Bu6PtLw+rV-e+-rgxXKpAwvdB0=vxeQ@mail.gmail.com>
References: 
 <CAEWfVJnbes69WFKpZjo-8Qu9zqqJwxC=G75ZxPtvEwFY4w+aQg@mail.gmail.com>
	<CA+ULb+v9cSAZs3Frsu8Bu6PtLw+rV-e+-rgxXKpAwvdB0=vxeQ@mail.gmail.com>
Date: Mon, 5 Jan 2015 18:27:50 +0100
Message-ID: 
 <CAEWfVJk=Wm878X=0MQGHFDUdLxHDSG-p2=oQNf0X6OZSe3wKAQ@mail.gmail.com>
Subject: Re: Podlings should be in charge of their mentors (was: Incubator
 report sign-off)
From: Bertrand Delacretaz <bdelacretaz@apache.org>
To: Incubator General <general@incubator.apache.org>
Content-Type: text/plain; charset=UTF-8

On Mon, Jan 5, 2015 at 6:21 PM, Roman Shaposhnik <roman@shaposhnik.org> wrote:
> ...What's difficult is the part
> that would require us to do something with poddlings put
> on hold. Unless we come up with clear exit criteria for
> this new state -- I don't think we're solving any real problems
> here....

A podling that's on hold is not adding committers nor making releases,
so they cannot make progress towards graduation.

They can then be managed in the same way as non-progressing podlings:
fail them if that state persists for too long. That's a minimal change
from how we're operating now.

-Bertrand

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org