You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by Om <bi...@gmail.com> on 2012/11/11 03:00:33 UTC
Re: Community patches are waiting
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" <ni...@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 <bi...@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
>
Re: Community patches are waiting
Posted by Nicholas Kwiatkowski <ni...@spoon.as>.
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 <bi...@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" <ni...@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 <bi...@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
> >
>
Re: Community patches are waiting
Posted by Michael Schmalle <mi...@teotigraphix.com>.
Quoting Justin Mclean <ju...@classsoftware.com>:
> Hi,
>
> Not being able to run Mustella (spaces in path issue which has now
> been fixed) and the length of time it takes to run the test have
> certainly been an issue for me.
This is the issue for me. For now I have to dedicate my time to my
paying future which sucks but is the reality. The framework is so
monolithic that it is becoming it's achilles heal.
We are seeing exactly why we have had the break down of Flex, it is
not modular and is killing any development of joe blo that is used to
more discrete projects on say GIT Hub.
I can honestly say I tried but, time wise it's to much for the little
time I have in my day as is. Hopefully that will change.
And we all know, if you have a modular framework, you shouldn't have
to test the whole thing since you decoupled any concrete dependencies
through interfaces or whatever.
Mike
Re: Community patches are waiting
Posted by Alex Harui <ah...@adobe.com>.
On 11/11/12 4:44 AM, "Justin Mclean" <ju...@classsoftware.com> wrote:
> Where is the selector documentation? Unless it's the caseName options It
> doesn't seem to be on the main Mustella wiki page [1]. I'm missing something?
The main wiki page is here [2] and the "selector" is one of two utilities in
the "Utilities" section. And there are a few words on how to use it here
[3].
[2] https://cwiki.apache.org/FLEX/mustella-overview.html
[3] https://cwiki.apache.org/FLEX/bug-fixing.html
>
>> Personally, I'm still focused on things like the FalconJS donation (which
>> was cleared legally last night, now needs signatures and other stuff).
> That's good news. Any news on progress with donation of BlazeDS?
There is another team who owns that donation. A month or so ago they said
"soon". I'll check in with them this week.
>
> Thanks,
> Justin
>
> 1. https://cwiki.apache.org/FLEX/apache-flex-incubating-wiki.html
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: Community patches are waiting
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
Not being able to run Mustella (spaces in path issue which has now been fixed) and the length of time it takes to run the test have certainly been an issue for me.
> The test selector is checked in and documented on the Mustella wiki page.
> I'm sure both the selector and the documentation need improvement, so give
> it a run and provide feedback.
I'll give it a run though in the next week and provide some feedback.
Where is the selector documentation? Unless it's the caseName options It doesn't seem to be on the main Mustella wiki page [1]. I'm missing something?
> Personally, I'm still focused on things like the FalconJS donation (which
> was cleared legally last night, now needs signatures and other stuff).
That's good news. Any news on progress with donation of BlazeDS?
Thanks,
Justin
1. https://cwiki.apache.org/FLEX/apache-flex-incubating-wiki.html
Re: Community patches are waiting
Posted by Alex Harui <ah...@adobe.com>.
On 11/10/12 6:00 PM, "Om" <bi...@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?
The test selector is checked in and documented on the Mustella wiki page.
I'm sure both the selector and the documentation need improvement, so give
it a run and provide feedback.
> 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?
Personally, I'm still focused on things like the FalconJS donation (which
was cleared legally last night, now needs signatures and other stuff). I've
been hoping other committers would jump in on the patches, especially
because we are now discussing graduation and the list of initial committers
might get culled to those who have actually checked something in.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui