I'm with you Om. Now that we all have clear that we want 9# as a result of the voting, it's a matter of getting the pieces enter in the puzzle. The main thing here IMHO is that we choose for a model of future and we, as a team, should row towards that goal.
2012/8/16 Om <bigosma...@gmail.com> > On Thu, Aug 16, 2012 at 1:24 AM, Justin Mclean <jus...@classsoftware.com > >wrote: > > > Hi, > > > > I raised several concerns but lets not go over that ground again. > > > > We'll need to have some documentation on how it's going to work and what > > SVN commands we need to use in each case. Anyone want to help out with > this? > > > > We have a few people who don't know both SNV and Git well and no one used > > Gitflow before (that I know) so even some simple guidance/instructions is > > going to help everyone. > > > > >> How do we share the local branches that would exist in git? > > > That may be one thing we can't do, but I don't think that was in the > > > diagram, but I'm also not familiar enough with Git to say for sure. > > > > Most of the branches shown in the digram are local and only master and > > develop are central in my understanding. > > > > Thanks, > > Justin > > > It is going to be a bit before we can answer all these questions. From the > git branching model, we need master (trunk) and the develop branch right > away. I believe everything else can wait and we can do it when needed. > Any reason we need to branch right away? I am not aware of any major > 'feature' branches or a release imminently coming up. > > Thanks, > Om > -- Carlos Rovira Director de Tecnología M: +34 607 22 60 05 F: +34 912 35 57 77 <http://www.codeoscopic.com> CODEOSCOPIC S.A. <http://www.codeoscopic.com> Avd. del General Perón, 32 Planta 10, Puertas P-Q 28020 Madrid
