title: Organization of Git (EGit) repository containing multiple project release versions
body: <p><strong>Question:</strong> What are some recommended ways of storing independent release versions of an eclipse project in a Git (EGit) repository?</p>
  
  <p><strong>Problem:</strong> I have been creating a new eclipse (python or 'pydev') project every time I want to distinguish it as a new release (so my projects are project_0-0-1, project_0-0-2, ..., project_9-9-9). I'm becoming suspicious that git may be more sophisticated than I think (and there are easier and more organized ways of such storage between release versions. Are there?</p>
  
  <p><strong>Details:</strong> I'm specifically interested in how to set this up using Eclipse egit. Would be nice if an answer included a short "how-to" (what buttons to click in the gui). I'm pretty good with egit but a far cry from anything labeled as "proficient". Also, I'm just looking for advice mostly - any ideas are kindly appreciated.</p>
  
  <p><strong>Research:</strong> </p>
  
  <p>I see some people have hinted git really isn't meant for this (it is version control not project management software):</p>
  
  <p><a href="https://stackoverflow.com/questions/14336243/versioning-and-release-management-with-multiple-products-with-shared-code-base">Versioning and release management with multiple products with shared code base</a></p>
  
  <p>Otherwise, would I just store different versions in branches? This is tempting but scary if I were to ever click "merge" by accident (maybe that's easily reversible though). I think that's what the links below are suggesting:</p>
  
  <p><a href="https://stackoverflow.com/questions/1238992/branch-master-tag-revision-increments-using-git">Branch/master tag revision increments using Git</a></p>
  
  <p><a href="https://stackoverflow.com/questions/9900889/git-tag-release-version">Git tag release version?</a></p>