The current situation with the C code for iron in our company:

  1. I have to write for several devices;

  2. each device has several modifications that affect the source;

  3. It is necessary to support several versions of the code for each modification of iron.

As a result, there is always a question of controlling whether each revision of the source code enters the necessary branches of the version control system. In this case, the engineer correcting the error in the code for a specific iron model often does not know where else this solution may be needed.

I would like to know what systems / approaches / workflow used in a similar situation. Maybe there are programs that allow you to visually display the relationship between: branch, commits, bugs ... and put down for each edit where else it needs to be ported.

  • The Git system has proven itself well. I can recommend the book Pro GIT - it describes the basics and principles of work well. - Peter K.
  • Git is used here, but it will not show the big picture. I suppose that you need to write your own plugin for Redmine or even a separate application ... - Dmitry-T
  • In other words, when we look at a task or a bug, it should be obvious which branches have already got edits, and which have not, well, of course, we need to be able to mark branches into which it is not necessary to transfer edits. - Dmitry-T

0