Merging from stable to trunk
- Check-out trunk
- Move to the root directory where you have your clean copy of trunk
- Using the command line at the trunk directory, run php doc/devtools/svnbranchupdate.php branches/version_number
- Example: php doc/devtools/svnbranchupdate.php branches/12.x
- Make sure your version of trunk is up to date and there are no uncommitted changes
- You should not even update composer, only svn up - it is best if this is a totally clean, dead copy of trunk.
- This command is pointing to the branch on the repository, not your copy
- Fix conflicts and commit using svn commit -F svn-commit.tmp.
- If there are conflicts that you cannot fix, try svn revert ./ to reverse the merge and notify the dev mailing list
- Whatever you do, don't just commit parts of the changes as that results in changes getting missed between the versions
You can ignore the message svn: Write error: Broken pipe.
If you are new to this and don't want to have a conflict to resolve: wait for someone else to merge and then do your changes on 12.x and right after, merge to trunk.
If you are outside this period, you can manually merge a commit: http://dev.tiki.org/Merge a commit to trunk" class="wiki wikinew text-danger tips">Merge a commit to trunk
Q & A
Q: How to test if it is a dead trunk copy ?
A: ...
Q: How do I check there is a conflict ?
A: ...
Q: How to resolve conflicts ?
A: In GNU/Linux, you may be able to use "Meld" as an external tool to resolve conflicts, and configure subversion to launch it when needed with the option l. See:
line edited in the /root/.subversion/config (and /home/xavi/.subversion/config ) files:
Once you saved your edit in the left pane (according tot he config explained in the example at the previous url), you can exit Meld, and if you are happy with your changes, mark that conflict as resolved typing the letter "r".
And the script is:
Alias names for this page: