Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
Received-SPF: pass (athena.apache.org: domain of mwessendorf@gmail.com
 designates 74.125.82.171 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:cc:content-type;
        b=fV4UzDqVXFVY7mWIPn98Og/usc56S4wEreKKcd1Pmhqnywl+mj0+6iptfIHRqRTduB
         gCajEzAabz6eAWlWIPqkHFMYIz1SmGELXxhMEt7ainrqFhr0jBu3riJXqmzSck0BtDV0
         o7aJf2SL/AKa/ALioim6eM1Edh3oL/wjMFwdg=
MIME-Version: 1.0
Sender: mwessendorf@gmail.com
In-Reply-To: <AANLkTinMaiYOmK5oCMJaXTQj_hn_9A-ghgZUzFj7Prxq@mail.gmail.com>
References: <87y6ceh8l3.fsf@v35516.1blu.de>
	<C886AA4F.1AF9F%Chris.A.Mattmann@jpl.nasa.gov>
	<AANLkTinMaiYOmK5oCMJaXTQj_hn_9A-ghgZUzFj7Prxq@mail.gmail.com>
Date: Thu, 12 Aug 2010 11:58:06 +0200
Message-ID: <AANLkTinVFXsTpxd3OrKGc9qMKkUaGhwiJUnq1GPVe1uw@mail.gmail.com>
Subject: Re: Future of RAT
From: Matthias Wessendorf <matzew@apache.org>
To: general@incubator.apache.org
Cc: "rat-dev@incubator.apache.org" <rat-dev@incubator.apache.org>,
	"dev@commons.apache.org" <dev@commons.apache.org>
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Aug 11, 2010 at 1:26 AM, Sanjiva Weerawarana
<sanjiva@opensource.lk> wrote:
> On Tue, Aug 10, 2010 at 7:33 PM, Mattmann, Chris A (388J) <
> chris.a.mattmann@jpl.nasa.gov> wrote:
>
>> I feel kind of the opposite -- RAT is an important tool that's required of
>> all the Incubator projects, but pretty widely integrated (at least in Java
>> land) outside of the Incubator as a tool to help check ASF policies. To me,
>> that's a big scope and an important community, and just based on the
>> telltale signs it seems like a TLP to me.
>>
>
> RAT is a superb tool and its not only for ASF. In WSO2 we have now started
> to use RAT on releases .. still early stage (and RAT is finding lots of
> issues) but the plan is to incorporate it into the nightly build process so
> we catch issue early. I am certain RAT will keep growing to handle more
> complexity and scenarios and it makes sense for it to become its own thing.
>
> So totally +1 from me to going TLP.

same here.
+1 for TLP

>
> Sanjiva.
> --
> Sanjiva Weerawarana, Ph.D.
> Founder, Director & Chief Scientist; Lanka Software Foundation;
> http://www.opensource.lk/
> Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
> Member; Apache Software Foundation; http://www.apache.org/
> Director; Sahana Software Foundation; http://www.sahanafoundation.org/
> Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
>
> Blog: http://sanjiva.weerawarana.org/
>


-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org