Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8277731
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 8, 20262026-06-08T08:46:19+00:00 2026-06-08T08:46:19+00:00

I work in a small development office, with 7 programmers, and we’re currently implementing

  • 0

I work in a small development office, with 7 programmers, and we’re currently implementing Git version control — we had no version control system before. Better late than never, right?

Having said that, we’re thinking about implementing the following structure:

Development server

  • Main repository – development’s stable version
  • Developer repositories – development repositories, one for each developer

Testing server

  • Main repository – stable testing version. modifications are pushed from the main development repository

Production server

  • Main repository – modifications are pushed from the main testing repository

Is this structure appropriate or am I missing the point of distributed version control systems? Can someone throw me some pointers or practical examples?

Edit1:

I appreciate all of your feedback, guys – things are clearer now. I understand that a structure like developer repos (local), development (bare) repo, testing repo and production repo would be a more logical choice and I can even see why some consider the development repo an unnecessary step.

I guess we’ll do some tests and see which structure we like the most.
Thanks

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-08T08:46:22+00:00Added an answer on June 8, 2026 at 8:46 am

    This is more or less about it. These are somethings you should note though:

    • Make the “Main repository” on development server a bare repository.
    • The developers don’t need to have a repository for themselves on the server, but they have a copy of the main repository locally on their own computers.
    • Every developer should fetch/merge from the main development repository and resolve conflicts before pushing back.
    • Don’t push to the test and production servers. From those repositories, fetch and merge from development and test servers respectively. This is because those repositories are not bare, and may in fact have commits of their own.
    • Have one guy (or one of the developers) responsible for fetching changes from the test/production servers, merge them with the current stable and push them to the main repository. This way, bug fixes in the test server are merged back in the development.
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I work in a small iPhone development team, in our office, we have at
I work for a small website company (couple of programmers, couple of designers). Currently
We work with a small development team and a system engineer who deploys the
I work on a small Agile development team which is part of a large,
I work at a small company, and we connect to our development environment via
At my work we recently finished the system architecture for a control application which
I am setting up our (relatively small) programming team to work with source control.
I have recently joined a small development team that is considering a new version
I host a small development server on my system. From that working directory I
I work in at small .net shop where we currently build all our solutions

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.