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

Revisions vs versions

From: Michele Manzato <michele.manzato_at_bigfoot.com>
Date: 2003-01-11 17:56:11 CET

Hello there,

(don't know if this is the right place to post. Tried looking for a newsgroup
or a user questions mailing list...)

I'm just wondering how did the "0.15.0" Subversion's release number
came out of the "3687" repository revision number. Was it a (more or less)
'manual' choiche or has it been automatically generated?

Coming to the real question. I usually manage several (>20) software modules
(libraries, programs, scripts, ...) each of which evolves in time across
various versions. Everytime I add a feature or fix a bug I make a new release
with a "manual" version number update (e.g. from 2.0.1 to 2.0.2). To date
this has been a nightmare, esp. because a) there are so many modules and b) I
have been using CVS and CVS tagging/branching is a real mess. Subversion
seems to be much better, still it does not seem to support version numbers,
(something like those provided by "arch")

Now I would *really* like to find a way of automating the process of deciding
new version numbers by means of some kind of scripting. A script like:

        release <path-to-module>

whose behaviour (for example) is to detect the current x.y.z version of the
module, add one to the rightmost digit x.y.(z+1) and produce the relevant
svn tags/branches. So:

a) is there anybody else having a similar kind of interest/feeling?
c) does SVN deal with this kind of problem? will it in the future?
d) did anybody ever develop similar scripts for SVN (or even CVS)?

Thanks a lot

Michele Manzato
michele.manzato at bigfoot dot com

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Jan 11 17:54:51 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.