What strategy use to choose SVN for a small team?

Warning: count(): Parameter must be an array or an object that implements Countable in /home/styllloz/public_html/qa-theme/donut-theme/qa-donut-layer.php on line 274
0 like 0 dislike
At the moment, just iterate through various versions, but the build trunk has several times been hell. There is a suspicion that the approach is initially crooked.
by | 4 views

1 Answer

0 like 0 dislike
To put the build on pre-commit-hook? Will be executed each time on the server without a successful build, commit reject. Although it will be slow, I suspect. The whole point of SVN is lost.

I agree with the concept of small atomic commits from the review pi314. But for this we need to decouple the build from a commit that is possible only in a distributed VCS. Alone is using SVN, Git find over-engineered and heavy. Glancing in the direction of Fossil, in case not yet tried.

Related questions

110,608 questions
257,186 answers
27,920 users