Hi, >> We've a Git repo, and master develop is the regular structure. > Then why does github assume trunk is the default and not develop? Can we get > this changed? > > Every other major Apache project I've looked at uses trunk/master for regular > updates: > https://github.com/apache/lucene-solr > https://github.com/apache/httpd > https://github.com/apache/ant > https://github.com/apache/subversion > https://github.com/apache/cassandra > https://github.com/apache/maven > https://github.com/apache/couchdb > > Why are we special/different? Because those repos are svn mirroring in git/github they're not really Git repos, in fact, if you review our flex-sdk repo in GitHub, you can found a trunk branch, from svn legacy. In fact I hope that infra's people removes this svn branches on github from full git migrated repos mirror, to avoid these confusions
>> We must avoid mixing the things, to avoid the confusion increment > How does working in develop avoid this especially as we have to merge into > trunk on each release. Well, most of Git applications, assumes these structure (master/develop/origin) to work, and is global agreement of use >>> -1 to move to old "trunk" svn layout. > I'm not suggesting that, I just suggestion that everyday work happen in the > trunk/master branch rather than the develop branch as this is the branch that > tools and people tend to look at by default to see what's going on. Well, we're free to rename our branches as we like it, at least the majority of them, but "master" must be preserved it's a Git requeriment. I just referred to best practices of use with Git like (master/develop) agreement. > Thanks, > Justin Thanks, -- Jose Barragan Chief Software Architect Codeoscopic Madrid C/. Infanta Mercedes, 92. Planta 5. 505. 28020 Madrid. Tel.: +34 912 94 80 80
