Jim Schneider <[EMAIL PROTECTED]> writes: > This should be handled by your release building tool (a feature that > seems an obvious no-brainer, once it's been pointed out that it's > missing).
Yes, and no. In general, a package has a version associated. For this version number the release building tool is a good way to have it incremented. But for all the individual modules that are part of a package? Their version numbers should only increase when something changed, i.e., at commit time. Not at release time. A task very neatly handled by CVS. And for which GIT c.s. has no alternative. -- Johan
