Mailing-List: contact general-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@incubator.apache.org
Received-SPF: pass (athena.apache.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
MIME-Version: 1.0
In-Reply-To: <1386836412.28313.58659173.641E53AC@webmail.messagingengine.com>
References: 
 <CAAS6=7h6GWJrvc88=xgc5O6xESZXK9K+TfMQGE7oGvA+cUEzyg@mail.gmail.com>
	<CAFk14gvSNJDfvmnbee4t0v0DiEVmnnm51_HtMga7MFDONs83rg@mail.gmail.com>
	<CAAS6=7hOBMmSvs4T0hFeRAYAXC9J-JDqFtj6z03BkVdqagD+jg@mail.gmail.com>
	<CALhtWkeBTj0Yi4UR-wnUVcQwJSDxmSi-f=2OCHJyuPQQCdvqNw@mail.gmail.com>
	<CAAS6=7gRwFWMAxQXNX=3C7UprGG2-1HQMWt7yaD2QXo+REDWFQ@mail.gmail.com>
	<CALhtWkdEeHzKXfLzacmC9CNyP5oC8jsh4wXs-d7O_yQe0ay62Q@mail.gmail.com>
	<CAJO+Ubu7tcafgtu6EEX+LEOgr_wKajoigPzGVRDAs58Gmv4xeg@mail.gmail.com>
	<CAAS6=7g0CSUpdS+YxB8-QtRwc6zMFE1t6Ho3TDqQ2_FJVFEW7A@mail.gmail.com>
	<1386836412.28313.58659173.641E53AC@webmail.messagingengine.com>
Date: Sat, 14 Dec 2013 20:41:44 -0800
Message-ID: 
 <CAAS6=7i_UPpfkW0oVBpiBMKwGsZVU-n4PRSg6-_esL2-1CqQ2g@mail.gmail.com>
Subject: Re: IP Clearance before releasing
From: Marvin Humphrey <marvin@rectangular.com>
To: "general@incubator.apache.org" <general@incubator.apache.org>
Content-Type: text/plain; charset=ISO-8859-1

On Thu, Dec 12, 2013 at 12:20 AM, Upayavira <uv@odoko.co.uk> wrote:
> We should probably be clear about *who* can relax the rules, because
> again this could become a fighting ground amongst 180 of us.

Perhaps we can avert potential disputes by blocking graduation rather than
releases.

Every review item in the following checklist is either required by Incubator
policy or is documented outside the Incubator as required for all Apache
releases:

    http://incubator.apache.org/guides/release_manifest.txt
    http://incubator.apache.org/guides/release.html#review-items

Let's say that we start allowing more documented exceptions to the rules for
incubating releases.  Fine -- but the podling still needs to demonstrate that
they can make a release worthy of a TLP, or they shouldn't graduate.

The simple approach is to establish a policy that a podling must make a
release which passes all the checklist items.  I'm sure we'd end up making
occassional exceptions under the "materiality" test, but that's no big deal.

An "audit" prior to graduation has also been proposed, but forcing IPMC
members to go rooting around in source trees, build scripts and issue trackers
seems unattractive.

Blocking graduation instead of release candidates would reduce strain on both
podlings and reviewers.  Suitable policy bugs could be fixed in between
incubating releases during the normal course of development, rather than
between release candidates -- so fewer release candidates would be needed.

Marvin Humphrey

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