The way I see it: #1 Pros: Uses Git. Therefore you only need to know one SCM. Any work with a rich branching history retains that history when landing in the main repos. #1 Cons: 240MB initial download. It took several hours for some folks.
#2 Pros: Not sure. #2 Cons: I think it would be hard to switch between branches when you have changes pending if you want to help out on someone else's whiteboard? Fred seemed to have other concerns. #3 Pros: Much easier to set up repos, I think. #3 Cons: Unclear about Apache approval. Have to be careful about who else contributes to your code. #4 Pros: Smaller initial download #4 Cons: Might be more work to transfer source from SVN to Git with history? For me, retaining history is way more important than waiting 2.5 hours once for the initial download. On 3/21/13 1:34 PM, "Om" <bigosma...@gmail.com> wrote: > Sorry, I have not been tracking the votes. Let me start up a new vote with > these options: > > =================================== > What to do with Whiteboard? > > 1. Use the sparse checkout option as described here ( > http://markmail.org/message/dg7hplezkzwiroes) > 2. Create a branch per user in the whiteboard > 3. Move to github for whiteboards > 4. Let whiteboards remain in SVN > > =================================== > > If there are more options, please add it to the discussion here. I will > give some time for discussion before starting an official VOTE thread. > > Thanks, > Om > > On Thu, Mar 21, 2013 at 1:30 PM, Frédéric THOMAS > <webdoubl...@hotmail.com>wrote: > >> Om, >> >> Btw, I remove my vote of 3.1 and give my +1 to the 3.4 (stay on svn), >> that's a lazy vote, I can change my mind ? >> >> -Fred >> -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
