|
|
Boost Testing : |
From: David Abrahams (dave_at_[hidden])
Date: 2007-05-05 08:39:17
on Sat May 05 2007, "Gennadiy Rozental" <gennadiy.rozental-AT-thomson.com> wrote:
> "David Abrahams" <dave_at_[hidden]> wrote in message
> news:87zm4k87rw.fsf_at_valverde.peloton...
>>
>> on Fri May 04 2007, "Gennadiy Rozental" <gennadiy.rozental-AT-thomson.com>
>> wrote:
>>
>>> "David Abrahams" <dave_at_[hidden]> wrote in message
>>> news:876478d51y.fsf_at_valverde.peloton...
>>>> * No way for a developer to request testing results for a specific
>>>> branch
>>>
>>> And against particular branch.
>>
>> How is "for a specific branch" different from "against a particular
>> branch?" it seems as though you're repeating what I meant to say (?)
>
> My library depend in lib A, B, C. I want to test against new_dev branch of
> A, HEAD branch of B and 1_33 branch of C.
So assemble a branch that contains everything you want, check it in,
and request the test. SVN is really good for that sort of thing
because of the way it copies "by reference".
>>> That's what independent versioning should address.
>>
>> I don't see a relationship between the two issues. The ability to
>> request test results against a specific branch has obvious utility;
>> you can try out changes and see how portable they are without
>> disturbing general test results. Independent versioning, by it self,
>> does not address that need. You'd still need to implement all the
>> same testing infrastructure, so I don't see the relevance here.
>
> Yes. independent versioning has little to do with "testing for a
> specific branch". But has everything to do with "testing against
> particular branch" ;)
I still don't see it, sorry.
-- Dave Abrahams Boost Consulting www.boost-consulting.com Don't Miss BoostCon 2007! ==> http://www.boostcon.com