Hi Greg, This is almost what I want, ie make a POC and once approved specifications and code, integrate it to the trunk, I do not see myself doing this POC directly into the trunk, but it may being is what is recommended, just that it makes me weird that way, can you confirm me that I have to start a POC in the trunk ?
Fred. -----Original Message----- From: Greg Reddin [mailto:gred...@gmail.com] Sent: Wednesday, November 21, 2012 4:26 PM To: flex-dev@incubator.apache.org Subject: Re: Apache Flex SDK Developer Tool Suite (was: Say "Hi" to 5 (!) new Apache Flex Committers) On Wed, Nov 21, 2012 at 2:52 AM, Frédéric THOMAS <webdoubl...@hotmail.com>wrote: > Yes, I didn't put any Apache Header yet but I thought to add them at > some point, this work if accepted has the goal to be re-integrated too > (but, tell me if I can't do it), notwithstanding, I prefer to work on > Git than svn, more flexible to me. > The crux of the issue is that it needs to happen here if you want to collaborate on it. We can't expect the developers to look in svn for one person's work and look in github, etc. for someone else's work. We follow commits in the Apache Subversion repo. Anything done elsewhere is not really part of the project until it gets checked in here.
