2010/11/12 Erik Huelsmann <ehuels_at_gmail.com>:
>> Do you think Subversion scales well for the following case, where
>> /trunk contains about 5000 files and its size is 500Mb
>> development requires 10 commits per day, 2-3 files changed per commit
>> on average.
>> Each commit is tagged (yes) from /trunk on the repository. How we will
>> test the tag is a separate issue.
>
> Why would you want to tag each commit? A commit is a tag in itself:
> there's a unique identifier to refer to the entire commit. This wasn't
> the case in PVCS, RCS and CVS, but there's really no reason to tag
> each and every commit; if you want to check out what got committed,
> just use the revision number!
Basically we need to test each commit from /tag while others proceed
on /trunk. Before we used to lock - modify - TEST [- correct bugs]
unlock. This really slows down the development because TEST is a long
period while development needs to be very frequent. Now with
Subversion we want to profit by concurrent progrommaing and testing.
Received on 2010-11-12 15:21:07 CET