Hi!
Tuesday, 24 September, 2002 you wrote:
KJ> Consider this. Lets say theres a large project with 20
KJ> engineers working on it. Lets say, in a week, each of
KJ> the devlopers makes 10 changes. That means that every week
KJ> the revision of the tree is increasing by 200. In a team that
KJ> size its likely to be much much more, however. Since most
KJ> developers are not coming to version control for the first
KJ> time, this can be a problem. We can all reamember fairly
KJ> low numbers, but what happens after two or three years of
KJ> active development, especially where even the slightest
KJ> change results in an entire tree reversioning? It gets
KJ> difficult to remember that revision 386419 had the fix
KJ> to the bug that was introduced at revision 353816.
With the speed you're talking about, you'll reach revision 353816
after more than 30 years of development :)
If you're concerned about simplicity of revision numbers you may
bump revision number every year (or month, or week) to some nice value
like xxx000 by performing an appropriate quantity of "dummy" commits.
Or, in a more general way, i suppose it's possible to add an ability
to subversion to refer to revision in the form <symbolic_tag>+offset
Then you'll be able to talk about revision 386419 as revision
"release_10_2_18+135" where release_10_2_18 is a symbolic tag of
revision 386284.
Egor. mailto:deo@logos-m.ru ICQ 5165414 FidoNet 2:5020/496.19
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Sep 24 12:49:04 2002