Disclaimer: this is *calm* and *quiet* reply.
On 5/26/07, Pavel Janík <[EMAIL PROTECTED]> wrote:
> What is the difference, for the end user, between two assembled
> cws, and the same in a milestone ?
He gets something predictable?
> *We have* aquavcl01 + aquafilepicker01 and for the ui, we have that
> too.
Yes, we have two separate child workspaces. There is no defined way
to get a build of two cwses in one build. And if they conflict, it is
impossible to do -> it doesn't make sense to mix them together.
My understanding of the point Pavel is making is that we get
additional benefits if we create the snapshots only from one cws.
Using only one cws makes it easier for other developers to make their
own builds *exactly* like the snapshot.
Example:
Developer A is working on a task of his own. He has his own
modifications in addition to normal cws aquavcl01 work. User B finds a
bug in publicly distributed snapshot from Mac porting project.
Developer A can help in solving the bug, because he can easily and
quickly compile his code so that it *exactly* matches the public
snapshot.
Best Regards,
Mox
