Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<h2>Version Control</h2> <p>Having a version control system is good, bug using it effectively is better. There are several ways to branch and merge effectively, two that might work for you are "per-feature" and "per-client".</p> <p><strong>Per Feature</strong></p> <p>In this setup, you create a copy of the main code (the trunk) for each new feature that you implement. Once the feature is complete, merge it back into the trunk. If you update the trunk before the feature is complete, or you complete a different feature, it is possible to merge those changes from the trunk into all of the branches.</p> <p><strong>Per Client</strong></p> <p>Same as per-feature, but each client gets their own branch, so that a feature rolled back for one is not removed from another. To combine the two, you might structure your repository like this:</p> <pre> Repos +---Core | +---branches | +---tags | \---trunk +---Client1 | +---branches | +---tags | \---trunk \---Client2 +---branches +---tags \---trunk </pre> <h2>Project Managemet</h2> <p>Now, to address your actual question. I can't really say much about this from experience, but I am planning to add <a href="http://trac.edgewall.org/" rel="nofollow noreferrer">Trac</a> to my project soon, because it looks simple to use, and it's free. You can see from their site how Trac's developers use their own application to set milestones and organize issues. If you want to look into more possibilities, then Wikipedia has a <a href="http://en.wikipedia.org/wiki/Comparison_of_issue_tracking_systems" rel="nofollow noreferrer">few</a> <a href="http://en.wikipedia.org/wiki/List_of_project_management_software" rel="nofollow noreferrer">lists</a>.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload