It's a code tree, not a code lattice

Are you trying to run a code tree or a code lattice?

Trees are less complex than lattices.

Sometimes things can go a little quirky with a merge and you have to get it sorted manually. These quirks come up more often with lattices, and are harder to figure out. If you are not careful you can end up with things like circular merges (which confuse some automated tools) and merges that end up taking or depending on code that is not the newest.

You can run your code repository any way you want, but I recommend sticking with a tree if you can.

If you think your devs would have trouble figuring out the difference, then yes, I would recommend you train up someone to be the SCM admin.

Are you trying to run a code tree or a code lattice?

Trees are less complex than lattices.

Sometimes things can go a little quirky with a merge and you have to get it sorted manually. These quirks come up more often with lattices, and are harder to figure out. If you are not careful you can end up with things like circular merges (which confuse some automated tools) and merges that end up taking or depending on code that is not the newest.

You can run your code repository any way you want, but I recommend sticking with a tree if you can.

If you think your devs would have trouble figuring out the difference, then yes, I would recommend you train up someone to be the SCM admin.

It's a code tree, not a code lattice

Are you trying to run a code tree or a code lattice?

Trees are less complex than lattices.

Sometimes things can go a little quirky with a merge and you have to get it sorted manually. These quirks come up more often with lattices, and are harder to figure out. If you are not careful you can end up with things like circular merges (which confuse some automated tools) and merges that end up taking or depending on code that is not the newest.

You can run your code repository any way you want, but I recommend sticking with a tree if you can.

If the reasons for this are not clear, then yes, you need to have a source code manager with appropriate training.

It's a code tree, not a code lattice

Are you trying to run a code tree or a code lattice?

Trees are less complex than lattices.

Sometimes things can go a little quirky with a merge and you have to get it sorted manually. These quirks come up more often with lattices, and are harder to figure out. If you are not careful you can end up with things like circular merges (which confuse some automated tools) and merges that end up taking or depending on code that is not the newest.

You can run your code repository any way you want, but I recommend sticking with a tree if you can.

If you think your devs would have trouble figuring out the difference, then yes, I would recommend you train up someone to be the SCM admin.