svn - Cherry picking features -
i've inherited legacy project must remain in svn.
originally branch created new release , several bug fixes made , deployed staging server. several times client asks bug 1 , 3 go production server causing lot of headaches.
what best branch strategy allow cherry picking of bugs?
i have 2 branches: "trunk" , "production". trunk contain latest version bugs fixed. production contain fixes requested production.
the development goes in trunk. periodically trunk selectively merged production (you select revisions merge every time).
Comments
Post a Comment