Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of omuppi1@gmail.com designates
 209.85.212.169 as permitted sender)
MIME-Version: 1.0
Sender: omuppi1@gmail.com
In-Reply-To: 
 <CALorpXdJBpH8smB3wn9cGXo_PFe0_k8E8zuzarD6pM0aNRmVOQ@mail.gmail.com>
References: 
 <CACK5iZcdOGsGUmm38d4SrdWrNSUY=fWMZMq7DtsEJxMNM1hLpw@mail.gmail.com>
	<CALorpXdJBpH8smB3wn9cGXo_PFe0_k8E8zuzarD6pM0aNRmVOQ@mail.gmail.com>
Date: Sat, 10 Nov 2012 18:00:33 -0800
Message-ID: 
 <CACK5iZfmB5_sMiyLBzPYcmk4UTcKuysPwtd7KPoWBSm3ym3wXQ@mail.gmail.com>
Subject: Re: Community patches are waiting
From: Om <bigosmallm@gmail.com>
To: "flex-dev@incubator.apache.org" <flex-dev@incubator.apache.org>
Content-Type: multipart/alternative; boundary=f46d044289eccf683304ce2e8ce8

--f46d044289eccf683304ce2e8ce8
Content-Type: text/plain; charset=ISO-8859-1

Nick,

Is that a systemic problem or is out a one off issue you are facing?

Alex,

How is your Mustella test selector app looking?  Reducing the number of
tests to run for each patch sounds like a good idea to increase the speed
of community patch acceptance.

Any other ideas?

Thanks,
Om

---------- Forwarded message ----------
From: "Nicholas Kwiatkowski" <nicholas@spoon.as>
Date: Nov 10, 2012 3:14 PM

My biggest issue is trying to build them against Mustella.  I broke my
mustella install locally, and haven't really fixed it in the last few
weeks.  I'm re-building it right now ;)

-Nick

On Sat, Nov 10, 2012 at 5:26 PM, Om <bigosmallm@gmail.com> wrote:

> Folks,
>
> There are quite a few community patches waiting to be reviewed and
> committed.
>
> I know we all are busy, but I am sure we can all find some time from our
> schedule to perform these duties we all signed up for.
>
> The longer we delay these important tasks, the more despirited the
> community will become about Apache Flex.
>
> What are the things that are preventing us from patching these very simple
> changes?  What can we do to be more efficient as a team going forward?
>
> Thanks,
> Om
>

--f46d044289eccf683304ce2e8ce8--