The leopard branch landing hasn't gone very smoothly. While the branch worked and was reasonably well tested on gutsy, feisty and leopard, testing of the branch code with Dapper, Windows and the older Mac versions was spotty at best.
Andi, bear and I have been fixing things, but many platforms are still broken. I do not advice you to do svn updates yet. However, it seems like the following are working: gutsy, full and quick, debug and release leopard on intel, full and quick, debug and release dapper, full and quick, debug and release These have problems: windows, localization check fails on some windows machines (tboxes in particular), some i18n tests may fail tiger/panther intel/ppc, unit tests run but chandler does not start, not quite sure what the problem is NOTE: You can ignore the l10n-linux Tinderbox until we get it to consistent green. NOTE: _gutsy-full-linux and _leopard-full-iosx are the only boxes for Gutsy and Leopard. They do full builds only, and currently don't do functional tests. Automatic binary tarball copy is offline until build problems have been fixed and the tool updated. In other words, all changes in external or internal will require hand building of binary tarballs. You may in some cases be able to copy manually from staging area, but you must be careful to ensure you have the right architecture bits to copy (currently the upload to staging does not make a difference between dapper vs gutsy, and leopard vs panther/tiger). -- Heikki Toivonen
signature.asc
Description: OpenPGP digital signature
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "chandler-dev" mailing list http://lists.osafoundation.org/mailman/listinfo/chandler-dev
