Thus, the advancing revision number marks the progress of the repository as a whole; you generally can't gauge the progress of a particular project within the repository by watching the revision number.Also, the revision number should not be used as the publicly-visible release number of a particular project in the repository.Server requirements depend on many factors, such as number of users, frequency of commits and other server related operations, repository size, and the load generated by custom repository hooks.
For that, you should devise some other mechanism of distinguishing releases, such as using tags.
The question is a bit loaded, because everyone seems to have a slightly different definition of "changeset", or a least a slightly different expectation of what it means for a version control system to have "changeset features".
The new revision number is a sequential label that applies to the entire new tree, not just to the files and directories you touched in that revision.
However, colloquially, a revision number is used to refer to the change committed in that revision; for example, "the change in r588" ("r588" is shorthand for "revision 588") really means "the difference between repository trees 587 and 588", or put another way, "the change made to tree 587 to produce tree 588".
FSFS repositories (introduced in version 1.1) do not have this restriction; however, due to a limitation in Win9x's file-locking support, they also don't work in Win9x.
To reiterate, the Subversion client can be run on any platform where APR runs.
A year later when we declared "alpha", Subversion was already being used by dozens of private developers and shops for real work.
After that, it was two more years of bugfixing and stabilization until we reached 1.0. However, if the client and server versions don't match, certain features may not be available.
Copyright © 2017 The Apache Software Foundation, Licensed under the Apache License, Version 2.0.
Apache, Apache Subversion, and the Apache feather logo are trademarks of The Apache Software Foundation.
(This is similar to how branches and tags are conventions built on top of copies, instead of being basic concepts built into Subversion itself.) Each time you commit a change, the repository stores a new revision of that overall repository tree, and labels the new tree with a new revision number.