On 8/14/12 2 :17PM, "Alex Harui" <aha...@adobe.com> wrote:
> > > >On 8/14/12 11:05 AM, "Gordon Smith" <gosm...@adobe.com> wrote: > >> I'd like to start a discussion of where Falcon will live in the Apache >> repository. >> >> The initial donation will be an Eclipse project and Ant scripts for >>building >> Falcon itself. Later we will donate another Eclipse project and Ant >>scripts >> for testing Falcon >> >> Although it is Java code, I don't think it should go into trunk/modules >>with >> the older compiler. It would be confusing to have a bunch of >>subdirectories in >> trunk/modules, some of which are for the old compiler and some of which >>are >> for the new compiler. So I propose that the two Falcon projects live >>inside >> trunk/falcon. >> >> Like the old compiler, Falcon is tied closely to the Flex framework >>because of >> the semantics of MXML. Therefore, I think Falcon belongs initially >>"inside" >> Flex, like the old compiler was inside Flex. Eventually, it would be >> interesting to try break many of these dependencies and let Falcon >>become its >> own project independent of the framework, but I see that as longer-term >> evolution. >> >> - Gordon >> >FWIW, keep in mind we also expect TLF to get VP signature this week as >well >and BlazeDS is in progress. IMO, All three are standalone entities and >should have top-level project status. I don't know how hard it is to move >the current trunk into an directory called sdk, but that would be my first >choice as in, when you go here: >https://svn.apache.org/repos/asf/incubator/flex/ > >You currently see: > branches > external > import2 > site > tags > trunk > utilities > whiteboard > >And I would like us to have: > blazeds > external > falcon > import2 > site > tlf > sdk > branches <-- these 3 are moved down from the top level > tags > trunk > utilities > whiteboard > >I'm not sure now is the right time to be moving trunk so I'd be willing to >live with some inconsistency right now and just have > blazeds > branches > external > falcon > import2 > site > tags > tlf > trunk <-- this is the current top-level trunk > utilities > whiteboard > >Thoughts? Regardless of whether falcon is top-level or under trunk, I think now is as good a time as any to go for your "I would like us to have" scenario since TLF will be arriving shortly. This is a very common Apache layout pattern. import2 should be deleted. I think it is confusing if the branches and tags that apply to trunk are lost in the list. I am going to have to add a tags directory to the utilities directory when we release the Install tool (but I see there is a problem already in that directory structure since there are 3 directories under utilities that will all need to be tagged). Carol
