The latest articles on DEV Community by Marmalade (@marmalade118). https://dev.to/marmalade118 https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F88392%2F9e308886-130c-4166-aa6f-9069cf8adb4e.jpg https://dev.to/marmalade118 en Marmalade Mon, 03 Sep 2018 10:23:57 +0000 https://dev.to/marmalade118/how-to-manage-different-project-release-versions-in-git-13pf https://dev.to/marmalade118/how-to-manage-different-project-release-versions-in-git-13pf <p>I'm relatively new to using Git and I was hoping someone might be able to help me out with a scenario I have found myself in?</p> <p>I have a requirement to create multiple versions of an app, each with a different feature set activated depending on the client's requirements; but also continue to develop a core feature set available to all versions.</p> <p>Initially I was going to put each version in it's own repository, but, from what I can tell, that would mean a lot more administrative overhead when releasing updates that are relevant to all versions, and isn't taking advantage of Gits features.</p> <p>I'm guessing the correct way to go with this is to use branches and merge the core updates in to each client specific branch but, I've only ever used Git to manage a single solution with a master, dev and sometimes a release branch, so I have no idea if this is the right or wrong way to go, how I would structure the repository etc.</p> <p>Any advice would be greatly appreciated.</p> help