
25 Aug
2010
25 Aug
'10
7:41 a.m.
Robert Ramey <ramey <at> rrsd.com> writes:
Actually this can be a big problem. I was having trouble testing on my own machine and in the trunk because boost.test was being worked on while I was using it. So I moved to lightweight test so that I would be dealing with only one thing at a time.
I do not believe this is *big* problem. Boost.Test is rather stable in a last couple years. You should be very unlucky to intersect with my update phase.
Now, I run all my local tests against the release branch of all the libraries not my own.
This is a good practice in any case and avoids any possibility of issues like above. Gennadiy