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
Date: Sat, 7 Dec 2013 15:43:35 -0800
Message-ID: 
 <CAAS6=7h6GWJrvc88=xgc5O6xESZXK9K+TfMQGE7oGvA+cUEzyg@mail.gmail.com>
Subject: 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

Greets,

I read in the Tajo report and I see on the dev list that the Tajo developers
are now diligently tackling IP clearance:

    http://s.apache.org/00w

    In my view, IP clearance is only the remain work for graduation.

However, the fact that this is only happening now represents a failure of the
IPMC.  Tajo made a release last month.  That release should not have gotten
our go-ahead until IP clearance was completed[1].

To address the immediate problem, it's important to complete IP clearance for
Tajo ASAP.  If everything goes well, I don't foresee any long term
consequences.  Let's cross our fingers.

For the future, the more rigorous release process being discussed in other
threads, which incorporates checklists and aggressively enlists the PPMC,
would have prevented this error.  (It would also have prevented the recent
Sirona error[2].)

Marvin Humphrey

[1] http://incubator.apache.org/projects/tajo.html
    http://incubator.apache.org/incubation/Incubation_Policy.html#Releases
    http://incubator.apache.org/guides/mentor.html#initial-ip-clearance

[2] http://s.apache.org/zjp

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