Hello, Tobias!
> > My former employer required testing on 2 platforms for check-ins on the
> > development branch and 6 (!!!) platforms for check-ins on the stable
> > branch. This could be acomplished with "views" in ClearCase, but CVS would
> > be of little help here.
>
> Why, this is a matter for branches, diffs, multiple "sandboxes", and some
> tags (for the bigger projects). It really is quite simple. And to you
> people that say "my sandbox is 100+MB, it's not practical, etc", I say
> "have you looked at the price of disk lately!?!"
So, you are suggesting "cvs checkin" as a way to move sources from one
machine to another? That's interesting.
Could you explain this idea in more details? Suppose that developers A and
B modify file test.c on machines M and N. Let's assume, for simplicity,
that they modify different functions, so there should be no conflicts.
The code is written and tested on M, checked in and then tested on N.
There are branches "not_tested_on_N" and "tested_on_N". A commits on M to
the branch "not_tested_on_N". B does the same. A updates on N and finds
problems in the code that [s]he didn't modify!
I don't want to commit my code that is not ready for "consumption" to any
branch that other developers may have access to. Maybe you are suggesting
personal branches?
Regards,
Pavel Roskin
