Function sections in CVS?

Question

I am obligated by policy to use CVS in this specific project, so even if I really switched to something else, like Git, I cannot.

So, my real question is this: we have an agreement that we create a new branch in CVS every time we make a release (we also note, but it’s not). We call these version branches, and they allow us to easily check a specific version and make corrections to it - this is what our earlier versions have.

But now I have some big changes associated with risk, and if I work in Git, I would instantly create a branch of signs. However, while working in CVS, I tried to create function branches in another project and found that everything quickly turned out messy. I ended up with a lot of branches, and I lost information about which branches were synchronized, what is needed for merging and which were no longer used.

So, getting closer to the question mark, is it possible to use branch functions in CVS? Are they too much trouble to be worthy of this, or do I end up eventually regretting not using them? Should I bite a bullet and just start coding in HEAD, but bend my coding process to make changes in the most unobtrusive way?

Answer 1

If you are the only developer on the feature branch, you can simply use Git as your sandbox development system, and then as soon as you make the changes, merge them into a CVS repository.

You still get the benefit of version control for your middleware product.

Answer 2

There is an excellent discussion of branching strategies called streamlines that can help - it describes the advantages and disadvantages of using function branches.

It also describes the code creation options and policies that you would like to implement.

Answer 3

, , - , , , . , .

, "".

, , "FEAT_MY_FEATURE" "FEAT_20080926" ( ?). .

Answer 4

, , . , , .

.

, ( , ), CVS , .

( ).

, - , , , Scrum.

SCM Patterns. .