The whiteboard was migrated from SVN, and I think folks did just copy SDKs in there so there is no common branch points. I wouldn't worry about a workflow for whiteboards, I want to get the workflow for flex-sdk, flex-falcon and flex-asjs in the wiki as that is where we have multiple folks working and where we are trying to use the nvie git branching model.
On 3/23/13 10:48 PM, "Michael A. Labriola" <labri...@digitalprimates.net> wrote: >> I'd rather see links to the best example elsewhere on the net or short >> stories as to what rebase does, or why cutting a branch saved your ass, along >> with steps to do it and what those steps are doing. Git seems >powerful >> enough that if you don't know what you are doing you can make a lot of work >> for yourself or others. > > Alex, > > Agreed. I think we will get there. > > Fred, > > As I am digging further into this though, I am coming up with a lot of > questions. I am guessing, based on the fact that I am seeing whiteboards, etc. > that committers don't really have their own forks in our current apache model, > but rather everyone is using their own clone of the same fork. Am I right? Is > there a particular reason we went this way? > > I am just trying to understand so I can do my best to guide us within the > model that has been created. There could be many viable reasons for this but > to me, right now, it's a little strange for a git project, so I am just trying > to grok it all. This would change some of the advice I gave Alex, for example. > > Mike > -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
