Change management

Question

I am currently working on a company that has several products with the same release cycle.

The problem I am facing is to create a release file that includes all the released files and for what changes. And there are several cases where customers roll back from a change close to the release date.

The difficulty I get is that every time I create a release file, I have to go through all the changed files and determine what the change is for, and cancel the change if the client decides to refuse.

Does anyone know the best change management solutions I can offer management?

Many thanks

Ps. I'm trying to look at the fight already, but I'm not sure that he is able to solve my difficulties.

Answer 1

Version control

Having a version control system is good; it’s better to use it with an error. There are several ways to branch and efficiently merge, two of which may work for you: "for each function" and "for each client."

In function

In this setting, you create a copy of the main code (trunk) for each new function that you implement. Once the function is complete, combine it back into the trunk. If you upgrade the trunk before the function completes or perform another function, you can merge these changes from the trunk into all branches.

For client

, , , , , . , :

Repos
+---Core
|   +---branches
|   +---tags
|   \---trunk
+---Client1
|   +---branches
|   +---tags
|   \---trunk
\---Client2
    +---branches
    +---tags
    \---trunk

Project Managemet

, . , Trac , , . , Trac . , .

Answer 2

, , Git, Subversion, Mercurial ..

, , , , SCM, TortoisSVN.

Answer 3

, ] project-open [, :

• ] po [ , .
• #ticket_id , [po] . ] po [intranet-cvs- . "CVS", SVN GIT.
• Finally, you need to create a script that applies the commits selectively to the code baseline, depending on the status of each change ticket.

Thus, you can automatically create your release files depending on the status of your change tickets.