It's systemic, but also self-inflicted. I guess it's the beauty of always being in the bleeding edge of every release of software that comes out. I think this latest time I customized my Java runtime because of some other software I was installing... Might have also been me hosing up Cygwin (which by the way -- if you are running on the Windows platform is still a pain in the rear).
I'm up and running and am check in on some of the submitted patches. -Nick On Sat, Nov 10, 2012 at 9:00 PM, Om <bigosma...@gmail.com> wrote: > 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" <nicho...@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 <bigosma...@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 > > >
