Menu
I have a solution in Subversion that I now will create a customer specific version of. It's unlikely that this version ever fully will get merged back into the main development. There will however be development both in the main trunk that I easily need to get into the specific project and the other way around (development in the custom project that needs to go back into the main trunk).
Should the new custom project be a branch that lives in parallel with the main development or a new project within the the same repository in your opinion?
687
New branch or "new campus" means a new site that houses a full range of instruction, as well as administrative and support services.
A Project branch is essentially an independent line of development checked out from the git branch. You can take advantage of Project branching when working on new features or bug fixes because it isolates your work from other team members. Creating a new Project branch does not change the repository.
Creating a branch from a previous commit Click History. Right-click on the commit you would like to create a new branch from and select Create Branch from Commit. Under Name, type the name of the new branch. Click Create Branch.
A repository is your whole project (directories and files) that you clone on your computer. A branch is a version of your repository, or in other words, an independent line of development. A repository can contain multiple branches, which means there are multiple versions of the repository.
I would definitely create a new branch. If the two variations of the project still share a lot of common code, and there's still even a remote likeliness they might be merged back together, I don't see any benefit in separating them into two totally independent projects.
I'd go with a branch - it gives you the options to later merge stuff back together, if needed.
Marc
142
If they are in the same repository, then it does not matter. You can still merge from the one project tree to the other.
Otherwise, my gut feel says "branch"
35
In theory this is a branch. So I would suggest to work with it as such.
45
I would say this is a branch. While you may not merge from the custom version to the head, its that likely code in the mainstream/head that you might want to migrate into your custom branch to upgrade the custom version. While this can be done in separate repositories its not as "visible" if its in a single place and when something falls off the radar it tends to lag behind and fall into disrepair.
34
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
