- Where Developers Learn, Share, & Build Careers


I am in the process of learning subversion, and by now I have learned one or two things, and I have a simple project To store, just created a Google code account and a svn repository, my problem is how to organize my svn repository. Imagine I just have an Android project called "Hello World" and a test project called "Hello World Test" Made, why Both projects should import my repository trunk? Does it make sense to put my exam project in the repository trunk?

SSIT in local file:

From the best practices suggested by Google: / P>

You can create a test project anywhere in your file system, but the best way is to add the test project so that its root directory is at the same level as the src / directory is the main application Project This helps you find the tests associated with an application Ta does. For example, if the root directory of your application project is a myofix, then you should use the following directory structure:

  MyProject / AndroidManifest.xml res / ... (Resources for the main application ) Src /. .. (source code for main application) ... test / AndroidManifest.xml Res / ... (resource for testing) src / ... (source code for testing)   < / Blockquote> 

in SVN repository:

The whole issue of fragmentation is for teamwork, the best way to use the structure of trunk / tags / branches is no doubt:

  Https: // svn / my-repo / MyProject / Branches / 1.1.1-Fork / Android Manifest XML Res / src / Test / Tag / Version 1.0.0 / Android Manifest XML Res / src / Test / Version 1.1. 0 / trunck / AndroidManifest.xml res / src / tests / AndroidManifest.xml res / src /    

How we usually use it:

  • Always checkout / commit from the trunk / during the time of development.
  • Before each release, tag the ready-to-release code (from the trunk) under the tag /.
  • If working with the same time (major changes) After a copy of the code below the branches (from the trunk) and started working on your branch, the next release to merge it back into the trunk.

    By my own experience, check the most efficient and appropriate structure (used for both local file system and version control system) for the group of projects, check.

Comments

Popular posts from this blog

Python SQLAlchemy:AttributeError: Neither 'Column' object nor 'Comparator' object has an attribute 'schema' -

java - How not to audit a join table and related entities using Hibernate Envers? -

mongodb - CakePHP paginator ignoring order, but only for certain values -