Re: Setting up the Apache CMS (was: the Flex website)

Hi Everyone, The site is now live and there are clues to how to edit the site if you are a committer. I am in the process of writing detailed information about Apache CMS for the OpenOffice podling. I've based the initial version of the Apache Flex website on a combination of that podling's s

Re: Setting up the Apache CMS (was: the Flex website)

Dave, that's great! some quick fixes: the SVN urls point to the ooo project and not the flex svn (on the FAQ and the Source Code pages) Dirk. 2012/1/5 Dave Fisher > Hi Everyone, > > The site is now live and there are clues to how to edit the site if you > are a committer. > > I am in the proc

Re: So, what should we do first?

Hi, I can safely say that I have a bit of experience using Subversion to manage a long running project with a big development team across several technologies and the one thing I'm pretty sure of is that, if not managed correctly from the onset, Subversion could be a nasty beast to handle. I'll

Re: Flex Framework rsl's

- Original Message - From: "Alex Harui" Adobe will not be caching RSLs from Apache so yes, we want to reduce the need for caching RSLs in the future. Alex, can you elaborate of the reasons of Adobe's choice? I really think the signed RSLs were one of the most important factor of Fle

Re: ACCOUNT

On Thu, Jan 5, 2012 at 7:42 AM, Saravanan G wrote: > Please create an @apache.org account for me.   I'd like > > the user id saravans. Are you one of the Flex initial committers listed at http://wiki.apache.org/incubator/FlexProposal ? (and if not, adding your name there is a no no of course ;-)

Re: Setting up the Apache CMS (was: the Flex website)

On Thu, Jan 5, 2012 at 9:00 AM, Dave Fisher wrote: > ...The site is now live and there are clues to how to edit the site if you > are a committer. Fantastic, thanks Dave! http://incubator.apache.org/flex/ looks so much better than my previous ugly temporary version ;-) -Bertrand

SVN SSH Keys

Hi everyone, Has anyone successfully set up their SSH key for SVN? I've been looking through the documentation online at Apache but I can't seem to find the instructions to setting that up. All I could find was a sentence that said upload your SSH key to a URL, I'm just not sure how I'm supposed t

Re: SVN SSH Keys

- Original Message - From: "Omar Gonzalez" Has anyone successfully set up their SSH key for SVN? I've been looking through the documentation online at Apache but I can't seem to find the instructions to setting that up. All I could find was a sentence that said upload your SSH key to

Re: Flex SDK code conventions

I've worked on a project where IntelliJ and Flashbuilder with FlexFormatter was used, it took a bit of tweaking but both IntelliJ's formatter and FlexFormatter can be configured to process files equally. So config files for both IDE's can be created and distributed. Other IDE's we'll need to look i

Re: Flex Framework rsl's

I'm pretty sure that will never happen, Adobe will never sign something that they're not responsible for. If Apache releases an SDK with a glaring security hole in it somewhere, Adobe will take the fall. Sorry for being pessimistic, but I don't see it happening. But I'll be glad to be proven wrong

Re: Flex SDK code conventions

Whatever formatting tool we use we should always make sure to separate reformatting from actual code change. It's a nightmare to review a 3 line bugfix when the patch contains 300 lines with formatting changes. When we agree on the codding standards and Adobe commits the code it would be worth to

Re: Flex Framework rsl's

From: "Roland Zwaga" I'm pretty sure that will never happen, Adobe will never sign something that they're not responsible for. If Apache releases an SDK with a glaring security hole in it somewhere, Adobe will take the fall. Sorry for being pessimistic, but I don't see it happening. But I'll be

Importing JIRA issues from Adobe Flex (was: Apache Flex source code - timeline for the initial code contribution)

Hi, On Wed, Jan 4, 2012 at 10:21 PM, Alex Harui wrote: > ...I am planning to transfer Flex JIRA issues to Apache JIRA.  It isn't a > straight export/import because we don't want to copy in some sensitive > information, and I want to have a mapping from Apache JIRA back to Flex > JIRA It woul

Re: So, what should we do first?

Just to expand on what I said earlier. I am hoping we don't agree on removing sandbox. Sandbox is a really important working area for each person. The big thing is that sandbox isn't just a giant dumping ground. Instead it is a giant dumping ground per person. This was I have my section of experim

Re: Flex Framework rsl's

In summit Adobe already said no. On Jan 5, 2012 3:37 AM, "DiMiTRi" wrote: > From: "Roland Zwaga" > >> I'm pretty sure that will never happen, Adobe will never sign something >> that they're not responsible for. >> If Apache releases an SDK with a glaring security hole in it somewhere, >> Adobe w

Re: [Account]

Hi, On Wed, Jan 4, 2012 at 6:30 PM, f...@rduartes.net wrote: >... Both the ICLA and my email change request reference f...@rduartes.net as > the new reference email address I still don't see an iCLA recorded with "duartes" in any field. -Bertrand

Re: So, what should we do first?

I dont understand why creating yourself a branch to create whatever you want isn't sufficient. Isn't that what branching is for? -omar On Thu, Jan 5, 2012 at 1:45 AM, Jonathan Campos wrote: > Just to expand on what I said earlier. I am hoping we don't agree on > removing sandbox. > > Sandbox is

Re: Flex SDK code conventions

Agreed, any formatting that is decided on should be initially applied in a single commit to the entire code base to prevent a two line commit from turning into 300 lines of changes listed in the commit log, and everyone should always format their code before committing, preferably on-save actions.

Re: So, what should we do first?

Hi Jonathan, I guess that what you refer to as Sandbox would be just a grouping of what I'm calling features branches, in a sense that we would have something like /sandbox/desktopCalloutButtonByJonathan, and this is what I was referring to a feature branches. That would in fact prevent Sandbox

Re: Flex Framework rsl's

I could live without signed RSLs and just use plain swf RSLs. Of course there is a nice benefit having them on FP cache but is it a crucial feature? Couldn't the SDK somehow be enhanced so we wouldn't even need it anymore? João Fernandes

I hate top posting

Hi Flex community, I'm just here as an incubation mentor so I'm not going to dictate anything (nor do I have the power to do so when it comes to such things), but I hate top posting and I'm seeing way too much of it for my taste here. How much in reverse are you reading to used don't I know, but

Re: Flex Framework rsl's

I agree here, ideally this feature should not be missed. The framework shouldn't be so fat that it requires this ugly workaround to begin with. -omar 2012/1/5 João Fernandes > I could live without signed RSLs and just use plain swf RSLs. Of course > there is a nice benefit having them on FP cac

Re: svn is ready

On Wed, Jan 4, 2012 at 12:25 PM, Bertrand Delacretaz wrote: > ...The following users should now be able to commit the flex subtree, > feel free to commit something (clever ;-) to > https://svn.apache.org/repos/asf/incubator/flex/trunk/SVN-TEST.txt to > verify FYI, just updated that list with

Re: Flex performance

Hi Jeffry, 2012/1/4 Jeffry Houser : > >  Has open Laszlo stayed up to date?  I hadn't heard of it in many years. The project has been maintained relatively well by Laszlo until early 2011, it seems the company has stopped development at the moment. I wasn't thinking of using OpenLaszlo directly.

Re: Flex Framework rsl's

Yes, it would be better if the framework would be more modular. Agree as well. 2012/1/5 Omar Gonzalez : > I agree here, ideally this feature should not be missed. The framework > shouldn't be so fat that it requires this ugly workaround to begin with. > > -omar > > 2012/1/5 João Fernandes > >> I

Re: I hate top posting

Good points, especially with regard to trimming and the search feature. - Raju

Re: I hate top posting

+1 - I'll take the joke opportunity anyway. :D On Thu, Jan 5, 2012 at 2:02 AM, Bertrand Delacretaz wrote: > Hi Flex community, > > I'm just here as an incubation mentor so I'm not going to dictate > anything (nor do I have the power to do so when it comes to such > things), but I hate top posting

Re: Flex Framework rsl's

I have mixed feeling about this. On one hand, there is definitely a point for improving the framework's modularity and split it in several normal rsl, but from my experience, several of the users of applications I've built, especially in the corporate/healthcare area, like to clean browser cach

Re: I hate top posting

> +1 - I'll take the joke opportunity anyway. :D > +1 :) In all seriousness, good points and if the post volume of this mailinglist continues as it is now good to have some best practices going. - Peter

Re: Flex SDK code conventions

2012/1/5 Iwo Banaś : > Whatever formatting tool we use we should always make sure to separate > reformatting from actual code change. It's a nightmare to review a 3 line > bugfix when the patch contains 300 lines with formatting changes. That would be excellent, if someone would be willing to do th

Re: SVN SSH Keys

> > Maybe the "Setting up SSH" section on http://www.apache.org/dev/new-** >> committers-guide.html >> would help > > Dimitri K. > I've read through that and I'm stuck on uploading the public key. I don't have a .ssh folder in my folder and whe

re: I hate top posting

Point taken and I'm sorry for being one of those people that do it. You're absolutely right and I'd very gladly +1 on that! Original Message > From: "Bertrand Delacretaz" > Sent: quinta-feira, 5 de Janeiro de 2012 10:28 > To: flex-dev@incubator.apache.org > Subject: I hate top

Re: I hate top posting

On 5 Jan 2012, at 10:02, Bertrand Delacretaz wrote: > IMO, the first part of http://en.wikipedia.org/wiki/Posting_style > describes the efficient Apache style of "inline posting with minimal > quoting" very well, and also IMO that's by far the style that works > best for serious discussions on a l

Re: So, what should we do first?

Hi, I'll comment on Rui's detailed description, as it's the closest to what I've seen in other Apache projects, large and small, and I think it might work well for Flex. On Thu, Jan 5, 2012 at 9:54 AM, f...@rduartes.net wrote: > ...1. I'd use a main TRUNK branch that would hold a releasable vers

First Flex release as soon as possible? (was: So, what should we do first?)

On Thu, Jan 5, 2012 at 1:42 AM, Alex Harui wrote: > ...I recall from the summit that a healthy Apache project releases at least > every 4 to 6 months, and one of the things an incubator podling has to do is > cut at least one release so it can show it knows the Apache way of doing so.   > So, wh

Re: I hate top posting

On 5 Jan 2012, at 10:02, Bertrand Delacretaz wrote: IMO, the first part of http://en.wikipedia.org/wiki/Posting_style describes the efficient Apache style of "inline posting with minimal quoting" very well, and also IMO that's by far the style that works best for serious discussions on a large lis

Falcon compiler source code / Falcon architecture

Alex, I read your reply in the asdoctool dicussion: 2012/1/4 Alex Harui : > Keep in mind that Adobe hopes to contribute Falcon at some later point in > time which seems to have a much cleaner code base to work from. Although it > isn't available now. Also keep in mind that the compiler source ma

Re: SVN SSH Keys

On Thu, Jan 5, 2012 at 11:17 AM, Omar Gonzalez wrote: >> >> Maybe the "Setting up SSH" section on http://www.apache.org/dev/new-** >>> committers-guide.html >>> would help >> > ...I've read through that and I'm stuck on uploading the public key

Re: Flex Framework rsl's

This arise the problem that the runtimes are still in Adobe's hands, something that Apache seems to not take care right now (thanks to god). If Flash Player was in Apache hands, this problem would not be a problem, since Apache will sign the RSLs. Meanwhile, we could ask Adobe to allow Apache sign

Re: SVN SSH Keys

> > I *think* our svn requires passwords sent over HTTPS, usually your > client asks for a password the first time you use a new repository. > I've got SVN working with my updated password, this is fine was just hoping to get an SSH key working so I didn't have to enter a password each time I comm

re: First Flex release as soon as possible? (was: So, what should we do first?)

+1 > I would suggest making a first Flex release much earlier than that, as > soon as possible, to get familiar with the Apache release process. I would go as far as to suggest that the first Apache Flex release should equivalent in code to the current Adobe Flex 4.6 release. This would guarant

Re: SVN SSH Keys

On Thu, Jan 5, 2012 at 11:46 AM, Omar Gonzalez wrote: > Bertrand: >> SSH keys work for ssh mys...@people.apache.org, not sure if they're >> used for anything else that committers do. >> >... > I tried putting a .ssh folder with my public key in it but SSH'ing into the > server still asks me for a

Re: SVN SSH Keys

> > ssh -v yours...@people.apache.org might help find out what's wrong. > > Thanks, I gave that a try. Seems its finding my SSH key on my laptop but it doesn't seem to find the key I placed on the server. I created my own .ssh folder in my user folder on the people.apache.org server but either I'm

RE: I hate top posting

> From: Bertrand Delacretaz [mailto:bdelacre...@apache.org] > Sent: 05 January 2012 10:03 > I'm just here as an incubation mentor so I'm not going to dictate anything > (nor do I have the power to do so when it comes to such things), > but I hate top posting and I'm seeing way too much of it for

FYI, http://incubator.apache.org/flex/team.html page added

Flex committers and mentors, please cross-check http://incubator.apache.org/flex/team.html ...and you can fix it yourself if needed, see http://incubator.apache.org/flex/developer-faqs.html#how_do_i_edit_this_website (I also added an ugly temporary logo to the website, to motivate people to creat

Re: Falcon compiler source code / Falcon architecture

Is there any documentation available explaining the differences between Falcon and the current version of the compiler? Or do you have a developer wiki for Falcon which might be shared with us, even if we don't have access to the source code, yet. Does the Falcon team already have an understand

RE: First Flex release as soon as possible? (was: So, what should we do first?)

+1 > +1 >> I would suggest making a first Flex release much earlier than that, as >> soon as possible, to get familiar with the Apache release process. >I would go as far as to suggest that the first Apache Flex release should equivalent in code to the current Adobe Flex 4.6 release. This woul

re: First Flex release as soon as possible? (was: So, what should we do first?)

+1 > I would go as far as to suggest that the first Apache Flex release should > equivalent in code to the current Adobe Flex 4.6 release. We can even keep the version as Apache Flex 4.6 to avoid the impression that we are releasing some new features. Cheers, Iwo Banas

Re: First Flex release as soon as possible? (was: So, what should we do first?)

+1 -Mensagem Original- From: Iwo Banaś Sent: Thursday, January 05, 2012 11:59 AM To: f...@rduartes.net ; flex-dev@incubator.apache.org Subject: re: First Flex release as soon as possible? (was: So, what should we do first?) +1 I would go as far as to suggest that the first Apache F

RE: Falcon compiler source code / Falcon architecture

+1 >Wouldn't it be important if the community had access to the Falcon source at a >very early stage? There are some great ideas here around creating an API for the compiler to support formatting and documentation tools for example. Also I'd like to experiment with adding custom generics sup

Re: Flex Framework rsl's

On 5 Jan 2012, at 10:29, f...@rduartes.net wrote: > On one hand, there is definitely a point for improving the framework's > modularity and split it in several normal rsl, but from my experience, > several of the users of applications I've built, especially in the > corporate/healthcare area, l

RE: Falcon compiler source code / Falcon architecture

Quoting David Arno : +1 Wouldn't it be important if the community had access to the Falcon source at a very early stage? There are some great ideas here around creating an API for the compiler to support formatting and documentation tools for example. Also I'd like to experiment with ad

re: First Flex release as soon as possible? (was: So, what should we do first?)

Quoting Iwo Bana? : +1 I would go as far as to suggest that the first Apache Flex release should equivalent in code to the current Adobe Flex 4.6 release. We can even keep the version as Apache Flex 4.6 to avoid the impression that we are releasing some new features. Cheers, Iwo Banas +1

Re: Falcon compiler source code / Falcon architecture

>I see this as a very important step in getting Apache Flex into the >melting pot viewed fairly along side other competing technologies. I >have had a few blog posts about the transformation of Flex and really, >this is exactly where it is going to happen on the low level. > >Mike +1

RE: First Flex release as soon as possible? (was: So, what should we do first?)

> From: Iwo Banaś [mailto:banas@gmail.com] > Sent: 05 January 2012 11:59 >> I would go as far as to suggest that the first Apache Flex release >> should equivalent in code to the current Adobe Flex 4.6 release. > > We can even keep the version as Apache Flex 4.6 to avoid the impression that

Re: First Flex release as soon as possible? (was: So, what should we do first?)

From: "Iwo Banas" I would go as far as to suggest that the first Apache Flex release should equivalent in code to the current Adobe Flex 4.6 release. We can even keep the version as Apache Flex 4.6 to avoid the impression that we are releasing some new features. I don't -1 it, but maybe this

Re: First Flex release as soon as possible? (was: So, what should we do first?)

+1 -Mensagem Original- From: David Arno Sent: Thursday, January 05, 2012 12:52 PM To: flex-dev@incubator.apache.org Subject: RE: First Flex release as soon as possible? (was: So, what should we do first?) From: Iwo Banaś [mailto:banas@gmail.com] Sent: 05 January 2012 11:59 I wo

Re: Setting up the Apache CMS (was: the Flex website)

agreed - very nice indeed! Carol -Original Message- From: Bertrand Delacretaz Reply-To: "flex-dev@incubator.apache.org" Date: Thu, 5 Jan 2012 01:03:00 -0800 To: "flex-dev@incubator.apache.org" Subject: Re: Setting up the Apache CMS (was: the Flex website) >On Thu, Jan 5, 2012 at 9:00

Re: First Flex release as soon as possible? (was: So, what should we do first?)

> I understand the "spirit" behind it, but I think there is so much to do right now, that putting some of "our" ressources in a "symbolic" release would not be a good first step in our new era. I don't consider this to be a "symbolic" release. It's more the release exercise and setting a baseline

Re: SVN SSH Keys

On Thu, Jan 5, 2012 at 12:15 PM, Omar Gonzalez wrote: >> >> ssh -v yours...@people.apache.org might help find out what's wrong. >> >> > Thanks, I gave that a try. Seems its finding my SSH key on my laptop but it > doesn't seem to find the key I placed on the server. I created my own .ssh > folder

RE: First Flex release as soon as possible? (was: So, what should we do first?)

+1 Dimitri, Even if the interest to be sure of the feasibility of the transition from the Adobe's model to the Apache one is important, this version should never be public for the reasons you mention, what do you think commiters ? Frédéric Thomas

Re: I hate top posting

On Thu, Jan 5, 2012 at 12:19 PM, David Arno wrote: > ...Your core message - that edited, bottom-posted emails work best with > Apache's archive facility and so could we please follow that convention - is > a good one. It's a shame you spoilt it by insulting myself and others by > suggesting you

Re: First Flex release as soon as possible? (was: So, what should we do first?)

On Thu, Jan 5, 2012 at 12:48 PM, David Arno wrote: > ...Not sure if I can +1 as I'm not a committer, so ignore this if I can't :) All opinions are welcome, so thanks for your +1. When voting (in a thread that's clearly identified by [VOTE] in its subject), only votes from PMC members (so PPMC in

Re: First Flex release as soon as possible? (was: So, what should we do first?)

On Thu, Jan 5, 2012 at 2:22 PM, Web DoubleFx wrote: > ...Even if the interest to be sure of the feasibility of the transition from > the Adobe's model to the Apache one is important, this version should never > be public for the reasons you mention, what do you think commiters ?... As far as th

Re: First Flex release as soon as possible? (was: So, what should we do first?)

I think the main objective here would be to reassure that the code base from the Apache Flex project stems directly from the Adobe code. Being able to run it through the existing tooling is an interesting side effect that I was not considering but could act as a test case of sorts in order to

Re: First Flex release as soon as possible? (was: So, what should we do first?)

From: "Bertrand Delacretaz" As far as the Incubator is concerned, a release doesn't exist if it's not public. So if the first Apache Flex release is not interesting to users, we should just label it as such, but it will still be public. Creating it will IMO be a very useful exercise for this pod

Re: First Flex release as soon as possible? (was: So, what should we do first?)

> >Creating it will IMO be a very useful exercise for this podling, and >it will be an important milestone towards graduating Flex. > >-Bertrand +1. I am the person who has been modifying the build files and source tree for the last couple of weeks in preparation for getting the code over to A

Re: So, what should we do first?

You took the word right out of my mouth. Perhaps it is beneficial to some people to make a mental distinction between types of development. On 1/5/2012 4:48 AM, Omar Gonzalez wrote: I dont understand why creating yourself a branch to create whatever you want isn't sufficient. Isn't that wh

Re: Flex performance

On 1/5/2012 5:04 AM, Raju Bitter wrote: I--personally--would rather see efforts put towards optimizing existing Flex Components or the component framework; not on creating a 3rd component framework within Flex. Agree, that will be more valuable at the moment. Just don't wouldn't close the doo

RE: I hate top posting

> From: Bertrand Delacretaz [mailto:bdelacre...@apache.org] > Sent: 05 January 2012 13:24 > I apologize if you feel insulted, that was not the intention - I thought that > by saying *I* hate top posting I made it clear that I'm just expressing an > opinion. A couple of people have pointed out t

Re: I hate top posting

I used to do in-line posting a lot; but stopped for a few reasons. Outlook seems to be designed for "top posting" and makes it hard to do in-line or bottom posting. The end result is that every corporate client I have does top posting and some get confused w/ in-line posting. Often the in

Re: First Flex release as soon as possible? (was: So, what should we do first?)

+1 It sounds like a good idea to do a simple release and keep messaging clear about it. As a next step, and to keep commits simple, I think working towards a 4.7 bug fix-only release might also be a good idea. I like the enthusiasm on the list for broad changes, but I am just worried about some o

Re: Proposition :: ASDoc and compiler adjustments

That would suck, but it's better than nothing. On 1/5/2012 1:27 AM, Alex Harui wrote: I poked around the Apache projects and found this: http://cxf.apache.org/javadoc/latest/ If you pick the class AegisDataBinding, you will see it inherits from java.lang.object which is not in the package lis

RE: First Flex release as soon as possible? (was: So, what should we do first?)

> From: Dimitri k. [mailto:k...@noos.fr] > Sent: 05 January 2012 13:37 > > Maybe it was more the talk about 3.5 Apache release that made me > worried we waste some steam on things nobody would use. Am I the only one stuck having to use 3.5 / 3.6 then? Or is it more the case that there is no be

Re: I hate top posting

On Thu, Jan 5, 2012 at 3:09 PM, David Arno wrote: >> From: Bertrand Delacretaz [mailto:bdelacre...@apache.org] >> Sent: 05 January 2012 13:24 >> I apologize if you feel insulted, that was not the intention - I thought that >> by saying *I* hate top posting I made it clear that I'm just expressing

RE: First Flex release as soon as possible? (was: So, what should we do first?)

>Valid points. >Maybe it was more the talk about 3.5 Apache release that made me worried we >waste some steam on things nobody would use. For what it is worth, We still have a number of clients using the Flex 3.x SDK

Re: Setting up the Apache CMS (was: the Flex website)

This placeholder logo is something I whipped up and is not owned by anybody. Just something visually impactful. - Randy On Thu, Jan 5, 2012 at 1:00 AM, Dave Fisher wrote: > Hi Everyone, > > The site is now live and there are clues to how to edit the site if you are a > committer. > > I am in th

Re: I hate top posting

Quoting Bertrand Delacretaz : On Thu, Jan 5, 2012 at 3:09 PM, David Arno wrote: From: Bertrand Delacretaz [mailto:bdelacre...@apache.org] Sent: 05 January 2012 13:24 I apologize if you feel insulted, that was not the intention - I thought that by saying *I* hate top posting I made it clear t

On voting (was:First Flex release as soon as possible?...)

On Thu, Jan 5, 2012 at 3:20 PM, Ryan Frishberg wrote: > ...@Bertrand, with regards to voting, does that mean we shouldn't respond > with "+1" unless the title of the thread is "[VOTE]". It's absolutely fine to use +1 to say "I agree", but unless the message subject says [VOTE] it never counts as

Re: First Flex release as soon as possible? (was: So, what should we do first?)

On Thu, Jan 5, 2012 at 8:03 AM, Dimitri k. wrote: > From: "Iwo Banas" > > I would go as far as to suggest that the first Apache Flex release should >>> equivalent in code to the current Adobe Flex 4.6 release. >>> >> >> We can even keep the version as Apache Flex 4.6 to avoid the impression >>

RE: First Flex release as soon as possible? (was: So, what should we do first?)

Quoting Jeff Tapper : For what it is worth, We still have a number of clients using the Flex 3.x SDK Jeff I would be interested in hearing "why" they are. Is this anything that could be changed in the future to allow larger companies to update easier on a major release? Is it becaus

Re: On voting (was:First Flex release as soon as possible?...)

Yes - the goal is to make sure people who only skim message headers quickly don't miss a vote. More info about voting at http://www.apache.org/foundation/voting.html -Bertrand So when functionality or implementation of SDK features need to be voted on what are binding votes in a [VOTE] ?

Re: First Flex release as soon as possible? (was: So, what should we do first?)

> > I would be interested in hearing "why" they are. Is this anything that > could be > changed in the future to allow larger companies to update easier on a > major release? In our case clearly the overhead introduced in the new spark architecture and advanced CSS was the main problem to migrate

Re: On voting (was:First Flex release as soon as possible?...)

Mike from what I've understood the community can share their votes but only official member votes will count for the final resolution. João Fernandes

RE: First Flex release as soon as possible? (was: So, what should we do first?)

> From: Michael Schmalle [mailto:m...@teotigraphix.com] > Sent: 05 January 2012 14:51 > I would be interested in hearing "why" they are. Is this anything that > could be changed in the future to allow larger companies to update > easier on a major release? > Is it because of the Halo to Spar

Re: On voting (was:First Flex release as soon as possible?...)

On Thu, Jan 5, 2012 at 3:54 PM, Michael Schmalle wrote: > ...So when functionality or implementation of SDK features need to be voted on > what are binding votes in a [VOTE] ? > > All community members, committers or just PPMC/PMC members? > > "Who" constitutes the approval? In a top-level projec

Re: First Flex release as soon as possible? (was: So, what should we do first?)

I have some projects running on 3.5 and for me it's fine with the current SDK as those projects just need to be maintained, not improved. I don't need an updated 3.x release. I would prefer resources to go into Flex 4.x On 05/01/12 15:44, "David Arno" wrote: >> From: Dimitri k. [mailto:k...@noos

Re: First Flex release as soon as possible? (was: So, what should we do first?)

On Thu, Jan 5, 2012 at 4:04 AM, f...@rduartes.net wrote: > I would go as far as to suggest that the first Apache Flex release should > equivalent in code to the current Adobe Flex 4.6 release. This would > guarantee that there is no gap in terms of code between the Adobe era and > the Apache era.

RE: First Flex release as soon as possible? (was: So, what should we do first?)

Largely, its very large enterprise applications which were started before the 4.0 release, and the cost/benefit analysis has shown they would not see a return on their investment from an upgrade to 4.x Many of our clients have upgraded old applications, but some have not, and are not likely to

Re: First Flex release as soon as possible? (was: So, what should we do first?)

Keeping the version number the same i.e Apache Flex 4.6 could prove confusing. Resetting the version number i.e Apache Flex 1.0, would break continuity with the prev SDK versions, and add to confusion Personally Flash Builder version number and Flex SDK version number was never a source of conflict

Re: First Flex release as soon as possible? (was: So, what should we do first?)

From: "David Arno" Maybe it was more the talk about 3.5 Apache release that made me worried we waste some steam on things nobody would use. Am I the only one stuck having to use 3.5 / 3.6 then? Or is it more the case that there is no benefit in diverting resources to improving Flex 3, so wh

Re: First Flex release as soon as possible? (was: So, what should we do first?)

On Thu, Jan 5, 2012 at 8:44 AM, David Arno wrote: > Am I the only one stuck having to use 3.5 / 3.6 then? No you're not. We'd really love to upgrade our apps, but there are bigger fish to fry. Greg

RE: First Flex release as soon as possible? (was: So, what should we do first?)

>My comment wasn't against a 3.5+ Apache branch. It was against doing a 3.5 >Apache release identical to the Adobe release one, like the 4.6 one is seems >everybody seem to agree on. >I know for a fact that lots of people are stuck in 3.x Flex. >Maybe one of the goals should also to adress the wh

[ACCOUNT]

Hi, Project PMC my ICLA has been filed. please use mschmalle for username and could you please change my account email from m...@teotigraphix.com to mschma...@teotigraphix.com ? Thanks you, Michael Schmalle

Re: [ACCOUNT]

On Thu, Jan 5, 2012 at 5:45 PM, Michael Schmalle wrote: > ...Project PMC my ICLA has been filed. please use mschmalle for username and > could you please change my account email from m...@teotigraphix.com to > mschma...@teotigraphix.com ? I see that the account request has been done already, so y

Re: Proposition :: ASDoc and compiler adjustments

Putting this on the top so the link is evident; http://blog.teotigraphix.com/2012/01/05/apache-flex-asdoc-and-compiler-tooling/ I said I would show you all what I am thinking about and what Roland says he is using is shown in the blog post above, the ASDoc Editor AIR application. I will be

Re: First Flex release as soon as possible? (was: So, what should we do first?)

Hi Randy, > I think releasing an identical version with the same version number > will cause confusion. Especially since the signed RSL issue has yet to > be sorted out. Let version 4.6 belong to Adobe. I would go so far as > to say to consider resetting the version number because it currently > s

Re: Flex Framework rsl's

There are no plans at this time to host RSLs somewhere. It might be possible if we get enough support for it. However, they won't be signed and I'm concerned about the security implications of that. I'm not a security expert, but I believe unsigned RSLs will leave you exposed to a man-in-the-mid

[ACCOUNT]

Hi, I think this time everything is OK as I've received confirmation on the receipt of ICLA. Could you please creat an @apache.org account? My preferred username is rduartes and I'm one of the initial commiters for the project (listed in the Flex Proposal page as Rui Silva (rui.silva at alert-

Re: Flex Framework rsl's

Alex, > I still hope to make RSLs an unnecessary thing in about two to three years. > More on that later after we get a first release out and I get some time to > work on it. You're definitely wetting my appetite! Let's see what you have in store! Rui

  1   2   3   >