Re: FalcoJs

On 5/7/12 9:08 PM, "Justin Mclean" wrote: > > Dare I ask if we have a rough idea of when the full Mustella tests might be > donated? (weeks away or months away?) Probably weeks. We're almost done with the scrub, but now we have to get the tests to run again. We could donate with tests broken

Re: FalcoJs

Hi, > I have to disagree about the no control part. Mustella got partially in this > week because some of you wanted it done that way. I could drop the rest of > mustella and start scrubbing the falcon js code but I thought we agreed that > a verification suite was more important. I think mos

RE: FalcoJs

"flex-dev@incubator.apache.org" >Sent: Sat, May 5, 2012 01:42:35 GMT+00:00 >Subject: RE: FalcoJs > >>:) True, my wording was too harsh for sure, I retract "100%". But my point >>was that the blog post wording originally was such that it very much made it &g

RE: FalcoJs

sympathy for Adobe communications. Sent from my Motorola ATRIX™ 4G on AT&T -Original message- From: "Michael A. Labriola" To: "flex-dev@incubator.apache.org" Sent: Sat, May 5, 2012 01:42:35 GMT+00:00 Subject: RE: FalcoJs >:) True, my wording was too harsh for

RE: FalcoJs

>:) True, my wording was too harsh for sure, I retract "100%". But my point was >that the blog post wording originally was such that it very much made it sound >like FalconJS was going to live or die based solely on >Apache Flex team, >whereas in reality at this point in time only Adobe has anyt

Re: FalcoJs

> it is not 100% factually incorrect. > :) True, my wording was too harsh for sure, I retract "100%". But my point was that the blog post wording originally was such that it very much made it sound like FalconJS was going to live or die based solely on Apache Flex team, whereas in reality at this

Re: FalcoJs

On 5/4/12 2:49 PM, "Doug McCune" wrote: > From the current blog post: > > "When FalconJS will become publicly available is now in the hands of the > Apache > Flex Team ." > > That's still 100% factually incorrect, isn't it? One could argue that be

Re: FalcoJs

> > The blog has been updated. Sorry for the confusion. > >From the current blog post: "When FalconJS will become publicly available is now in the hands of the Apache Flex Team ." That's still 100% factually incorrect, isn't it?

Re: FalcoJs

>>So why they updated that blog? >>It seems an offcial blog from adobe no? >> The blog has been updated. Sorry for the confusion. >Read this: >http://www.adobe.com/devnet/flex/whitepapers/roadmap.html > >Especially this section: >

Re: FalcoJs

thanks to both. I will checkout the project and start having a look to it. On 4 May 2012 18:58, Greg Reddin wrote: > On Fri, May 4, 2012 at 12:52 PM, filippo dipisa > wrote: > > How can I know what's going on? > > To over-simplify: by doing your work publicly. > > If you have a feature you want

Re: FalcoJs

On Fri, May 4, 2012 at 12:52 PM, filippo dipisa wrote: > How can I know what's going on? To over-simplify: by doing your work publicly. If you have a feature you want to implement (generics, for example), bring it up on the mailing list. Get some discussion started. Create a Jira issue and start

Re: FalcoJs

Posting an question to that effect on this list is a great start... you might even find a buddy to make the work go faster. R On Friday, May 4, 2012 at 1:52 PM, filippo dipisa wrote: > So basically at the moment, everyone can start whatever and then the board > decides if integrate it into a

Re: FalcoJs

So basically at the moment, everyone can start whatever and then the board decides if integrate it into a candidate release or not, right? Doing like that there could be a duplicate work, for example I could start work on implementing Generic and maybe there is another team doing it. How can I kn

RE: FalcoJs

>I understand, but could be useful also vote before writing the code no? >For example i could write 10 user stories and then If I see that nobody likes >them I don't event start to implement them. You are absolutely free to do so and get people's opinions of them. I was simply saying there isn't

Re: FalcoJs

I understand, but could be useful also vote before writing the code no? For example i could write 10 user stories and then If I see that nobody likes them I don't event start to implement them. On 4 May 2012 17:54, Michael A. Labriola wrote: > >Thanks for the clarification. > >Waiting Falco, in o

RE: FalcoJs

>Thanks for the clarification. >Waiting Falco, in order to contribute to apache flex I just have to checkout >the Flex code and then decide what to do, right? >have you got any agile tool containing the user stories and the sprint mapping? Yes, you just check out the code. However, apache doesn'

Re: FalcoJs

On 5/4/12 9:43 AM, "Michael A. Labriola" wrote: >> So why they updated that blog? >> It seems an offcial blog from adobe no? >> > > I understand the confusion, I really do. Much of Adobe isn't really good at > the communicating wi

Re: FalcoJs

Thanks for the clarification. Waiting Falco, in order to contribute to apache flex I just have to checkout the Flex code and then decide what to do, right? have you got any agile tool containing the user stories and the sprint mapping? On 4 May 2012 17:43, Michael A. Labriola wrote: > >So why th

RE: FalcoJs

>So why they updated that blog? >It seems an offcial blog from adobe no? > I understand the confusion, I really do. Much of Adobe isn't really good at the communicating with humans thing. I can absolutely 100% promise you we do not ye

Re: FalcoJs

So why they updated that blog? It seems an offcial blog from adobe no? On 4 May 2012 17:34, Michael A. Labriola wrote: > >FalconJS is in the queue after Falcon. All of these things take time. I > hope to beat Jeffry's time frame,

RE: FalcoJs

>FalconJS is in the queue after Falcon. All of these things take time. I hope >to beat Jeffry's time frame, but you never know. Let's clarify that for the moment. Neither are really in the queue because, at this point, Adobe (despite what that blog post errantly says) has not yet donated Falc

Re: FalcoJs

Can we help you in any way to see the code as soon as possible? On 4 May 2012 17:28, Alex Harui wrote: > > > > On 5/4/12 9:16 AM, "filippo dipisa" wrote: > > > When FalconJS will become publicly available is now in the hands of the > Apache > > Flex Team

Re: FalcoJs

On 5/4/12 9:16 AM, "filippo dipisa" wrote: > When FalconJS will become publicly available is now in the hands of the Apache > Flex Team . > FalconJS is in the queue after Falcon. All of these things take time. I hope to beat Jeffry's time frame,

Re: FalcoJs

wrote: > > On 5/4/2012 11:42 AM, filippo dipisa wrote: > >> Hi, >> I Just read that FalcoJS has been donated to the Apache Flex Foundation. >> Do you know where I can checkout the project? >> > Where did you read that? As far as I knew; FalconJS will not

Re: FalcoJs

On 5/4/2012 11:42 AM, filippo dipisa wrote: Hi, I Just read that FalcoJS has been donated to the Apache Flex Foundation. Do you know where I can checkout the project? Where did you read that? As far as I knew; FalconJS will not be donated to the Apache Foundation until the Falcon compiler is

FalcoJs

Hi, I Just read that FalcoJS has been donated to the Apache Flex Foundation. Do you know where I can checkout the project? Thanks Filippo