IMO, you can do it any time. There is no official binaries so if you've
built it, stick it up there.
-Alex
On 8/21/14 11:44 PM, "OmPrakash Muppirala" wrote:
>On Aug 21, 2014 11:26 PM, "Justin Mclean"
>wrote:
>>
>> Hi,
>>
>> And the votes passes with:
>> 4 +1 votes (Justin, Alex, Nick and Mark
On Aug 21, 2014 11:26 PM, "Justin Mclean" wrote:
>
> Hi,
>
> And the votes passes with:
> 4 +1 votes (Justin, Alex, Nick and Mark)
> 1 -1 vote (Om)
>
> And the following community votes
> 2 +1 votes (Chris and Tom)
>
> Thanks everyone for taking to the time to look and vote on this and
previous re
Hi,
And the votes passes with:
4 +1 votes (Justin, Alex, Nick and Mark)
1 -1 vote (Om)
And the following community votes
2 +1 votes (Chris and Tom)
Thanks everyone for taking to the time to look and vote on this and previous
release candidates.
Thanks,
Justin
Hi,
> If I have a vision or idea for something and go ahead and build it [and/or
> try to donate it];
That is certainly one valid path to take, but it then it may need to go through
a software grant and IP clearance. That's a cost you may need to incur if you
want to bring software to Apache in
Hi,
Obviously there a few things I can't say here re what has gone on on the
private list.
> Your actions seem to indicate otherwise.
Quite the opposite - please see the number and diversity of committers that I
have put forward to vote on. Several of which have become productive members of
th
Hmm. Looks like a bug in installer.xml.
Not that it should matter too much. We only cherry-pick a few things out
of there.
-Alex
On 8/21/14 4:12 PM, "OmPrakash Muppirala" wrote:
>I am trying to get back into FlexJS development after a while. One thing
>I
>noticed was when I was installing F
Hi,
> I happen to know that PMC member (it was me ;-)) and my resignation was for
> personal reasons totally unrelated to the issues Justin mentions.
I did not state the reason you left just that someone had.
> what you're doing now comes dangerously close to intentionally sabotaging the
> projec
I am trying to get back into FlexJS development after a while. One thing I
noticed was when I was installing FlexJS via the Installer was, it was
reusing the Flex SDK 4.12.1 from my local cache to create the overlay.
Shouldn't it be using the latest version, i.e. 4.13.0?
Thanks,
Om
Wow, it's Lee Burrows from Adobe, what a surprise~
I used to read some nice AS3 articles from him.
My guts is telling me Adobe may finally want to update their Flash Builder
product line, it's been too long, and desperately needs to be updated.
I guess they want to test the latest Flex SDK with
Hi,
Thanks for bringing that to our attention. We've been having server
issues on the Apache side. Should be ok now.
Thanks,
-Alex
On 8/21/14 1:56 PM, "Subscriptions" wrote:
>Hi All,
>
>Not sure if temporary or known issue but installer repeatedly fails to
>complete when selecting AIR/FP 15.
Hi All,
Not sure if temporary or known issue but installer repeatedly fails to
complete when selecting AIR/FP 15.
Here's my log:
Version 3.1.0 (windows)
Using Locale: en_GB
Fetched the SDK download mirror URL from the CGI.
AIR version 15.0b
Flash Player version 15.0b
Creating Apache Flex home
Hi,
> Don’t you think it’s a bit extreme declaring the PMC broken because some
> people disagree with you?
> I don't see it that way - there have many issues in recent months and
> we've had one other PMC member resign.
I happen to know that PMC member (it was me ;-)) and my resignation was for
Hi,
> Don’t you think it’s a bit extreme declaring the PMC broken because some
> people disagree with you?
> I don't see it that way - there have many issues in recent months and
> we've had one other PMC member resign.
I happen to know that PMC member (it was me ;-)) and my resignation was for
Okay. I don’t think this is the place for this, but if you want the discussion
here, I’ll respond.
>> Part of building community is allowing for the fact that there are different
>> points of view
> I'm all for that.
Your actions seem to indicate otherwise. Declaring the PMC broken and it needs
I, personally, don't understand the "openness" complaint here but I've
seen similar sentiments before.
If I have a vision or idea for something and go ahead and build it
[and/or try to donate it]; I should not be discriminated against because
I didn't discuss it on the list first. The com
Hi,
> I don't think we have a rule on it ATM. But for the SDK changes I usually
> close mine after a few days.
We generally don;t close them [1], but you can if you want.
Thanks,
Justin
1. https://issues.apache.org/jira/issues/?filter=12323441 (1500+ resolved but
not closed issues)
Hi,
> Don’t you think it’s a bit extreme declaring the PMC broken because some
> people disagree with you?
I don't see it that way - there have many issues in recent months and we've had
one other PMC member resign.
> Part of building community is allowing for the fact that there are different
Hi,
> Inappropriate to start a "the sky is falling" to an entire community.
The sky issn't falling and we can fix it.
Part of the key concepts of the Apache Way is openness and that's where I've
decided to go. I welcome anyones ideas and constructive feedback. You you can
email privately or m
I don't think we have a rule on it ATM. But for the SDK changes I usually
close mine after a few days. This allows for any objections and/or Mustella
breakages to appear.
-Mark
-Original Message-
From: Mihai Chira [mailto:mihai.ch...@gmail.com]
Sent: Thursday, August 21, 2014 5:52 AM
Inappropriate to start a "the sky is falling" to an entire community.
-Mark
Justin,
Don’t you think it’s a bit extreme declaring the PMC broken because some people
disagree with you?
Part of building community is allowing for the fact that there are different
points of view and just because there’s disagreement does not mean things are
broken. In fact, a community wit
As far as I could tell mustella's tests weren't affected by the
changes in HierarchicalCollectionViewCursor,
HierarchicalCollectionView and LeafNodeCursor made to solve
FLEX-34440, FLEX-34424, FLEX-34456, FLEX-34458, and the original
FLEX-34119.
I marked them all as resolved (including an extra on
Your friend may be interested in reading about this campaign [1]. As you can
see any amount is welcome, even no amount at all.
[1]
http://apache-flex-development.247.n4.nabble.com/New-public-Flex-related-campaign-td39682.html
--
View this message in context:
http://apache-flex-development
Hi,
I've considered carefully and so rather than resigning from the PMC I'm going
to see if I can fix it. Hopefully other PMC members can help me in this. If we
can't fix it I'll reconsider my options.
The PMC responsibilities are clearly spelt out here [1], first they are legal
and secondary
True
-Original Message-
From: "Justin Mclean"
Sent: 8/21/2014 1:12 AM
To: "dev@flex.apache.org"
Subject: Re: [DISCUSS] TourDeFlex Release Candidate 3
Hi,
> Can we at least remove the stuff that we know does not work? It should be
> straightforward to just remove it from explorer.xm
I do like that idea. And make it top of list to fix for next version. At least
that way we keep the known bug away as an eye soar for those interested in flex.
-1 vote for that
Chris
-Original Message-
From: "OmPrakash Muppirala"
Sent: 8/20/2014 11:59 PM
To: "dev@flex.apache.org"
S
Hi,
> Can we at least remove the stuff that we know does not work? It should be
> straightforward to just remove it from explorer.xml.
We would need to cut a new RC to do that as the signatures would change if we
made changes to the XML file. It not really on to deploy a file different to
wha
27 matches
Mail list logo
