Ion Gaztañaga wrote:
Beman Dawes wrote:
Until further notice, branches/release is open for known-good merges.
"known-good" means changes that are already passing trunk regression tests, or are in files like documentation that have no effect on testing.
Thus if you make a bug fix in trunk, wait a day or two before committing a merge of the fix to branches/release and look at the regression test results before you commit. Make sure in particularly the change doesn't break other libraries.
Sorry if this question is a bit silly, but where can I see the results of the release branch testing? Clicking "Release view" on the trunk does not show nothing. Interprocess still has 13 failures that I have to fix so I'd like to see how the release version is looking while I try to fix the issues on trunk.
Sorry if this has been previously answered,
NP... http://beta.boost.org/development/testing.html ...Has all the links to the various test results. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo