ATTN: Branch for release completed

Per our standard conventions, the branch tag is "RC_1_32_0", and the main trunk state from which the branch was performed is tagged as "merged_to_RC_1_32_0". Please see http://www.boost.org/more/release_procedures.htm#Developers for a detailed procedure for merging fixes between the branch and the main trunk. To regression runners using "regression.py" driver: to switch the tests to run on the branch, you need to specify the branch name in the script's command line using the '--tag': python regression.py --tag=RC_1_32_0 ... -- Aleksey Gurtovoy MetaCommunications Engineering

Aleksey Gurtovoy wrote:
To regression runners using "regression.py" driver: to switch the tests to run on the branch, you need to specify the branch name in the script's command line using the '--tag':
python regression.py --tag=RC_1_32_0 ...
Done, but it doesn't work right now. It seems that the tarball is not available yet; is it produced automatically for every branch? (I can't imagine...) Stefan
participants (2)
-
Aleksey Gurtovoy
-
Stefan Slapeta