[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Subversion Revision Numbers driving me Batty. What about a SECOND revision number?

From: Charley Bay <charleyb123_at_yahoo.com>
Date: 2003-10-22 14:02:02 CEST

> As a senior developer, the low revision nubers tell
> me one of two things:
> 1) This piece of code is extremely stable.
> or
> 2) This code coudl be extremely stale.

(3) The file is twelve minutes old, and it's only
changed 7 times. ;-)))

But, I *do* see the point about the value in
identifying 'change volatility' in a single file.
The second revision number (total touches to the file)
may be useful, but insufficient for me: Are the last
dozen touches in the last week, or two years ago?

If the number is to have 'meaning' beyond arbitrary
repository-wide iteration, I'd prefer to see a GUI
or tool make use of subversion APIs that allowed us
to access this type of information (changes specific
to files over time) with greater granularity.

For example, the tool (making use of some subversion
API) would present files as 'red', 'yellow', and
'blue' for how many times it's been touched since the
last release, or I'd simply histogram the number of
touches to a file or set of files in a directory
against time, and present a graph (yes, a real graph
as a 'tool tip' when the mouse hovers over the file
or dir).

If we had a second number specific to the file
('file touches'), I'd use it, but it wouldn't be the
granularity I'd prefer: I'd want time also.


Do you Yahoo!?
The New Yahoo! Shopping - with improved product search

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Oct 22 14:02:41 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.