RE: Vendor branches: Current guidance? [Fixed formatting]

Hello all,

[Repost with formatting fixed. Misbehaving email client.  ]

What are the currently accepted best practices / tools for maintaining "vendor" branches?  Particularly where maintaining patches against vendor drops is expected.

I've seen the page at:
http://svnbook.red-bean.com/en/1.7/svn.advanced.vendorbr.html

I ask about updated guidance since:

1) I notice some (?) churn for this section in the SVN Book repository:
https://code.google.com/p/svnbook/source/browse/trunk/en/book/ch04-branching-and-merging.xml

2) There appears to be both "svn_load_dirs" and "svn-merge-vendor.py" scripts at:
http://svn.apache.org/repos/asf/subversion/trunk/contrib/client-side/

I'm trying to refactor out some thirdparty code from my codebase, and I'd like to set things up correctly.  (I'd hate to screw things up just because I accidentally read a soon-to-be-outdated HOWTO.)

Secondarily, what kind of issues can I expect to encounter as I setup and use a vendor branch style deployment?

Thank you,
David
Received on 2014-05-22 21:35:11 CEST