On 08/31/2010 10:36 AM, Julian Foad wrote: > Bindings: swig-py, swig-pl, swig-rb all pass their tests. ctypes-python > fails to build for me. Java: Philip said "I've run javahl tests in > single-db, 3 FAILs compared to 1 in multi-db." > > Upgrading from a dev version: When the switch is made, after updating > and re-compiling, each dev using a trunk WC (format 18) will need to run > tools/dev/wc-ng/bump-to-19.py on the WC. > > Running the new svn on an format-18 WC will report a friendly message > advising you to use bump-to-19.py. (Running it on an older 1.7-dev > (format <= 17) WC will probably upgrade one directory to format 18 and > then exit with that message, which doesn't sound quite right.) > > Running an old svn on a format-19 (single-db) WC results in a friendly > error. > > I think we're all set to switch it on.
Ooh. Wait a second. I seem to recall that your Python script had some limitations -- couldn't handle externals, or something. Is that still the case? Can it be worked around by something like: 1. rm -rf /path/to/external/directory 2. bump-to-19.py 3. svn up ? -- C. Michael Pilato <cmpil...@collab.net> CollabNet <> www.collab.net <> Distributed Development On Demand
signature.asc
Description: OpenPGP digital signature
