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

Re: real quick answers about Subversion

From: Stephane Bortzmeyer <bortzmeyer_at_nic.fr>
Date: 2005-10-05 15:10:54 CEST

On Wed, Oct 05, 2005 at 08:39:51AM -0400,
 Frank <fgeck@optonline.net> wrote
 a message of 155 lines which said:

> * Did not see a way to help to manage the entire development
> process. I.e. some one issues a change request (i.e. tester for
> example) that would get assigned to a developer (i.e. some admin
> or board member to do it) etc. I.e. some way to really track
> that change through a well defined process.

This is not the job of a VCS like Subversion. It is a job for a
project management tool like Trac (http://www.edgewall.com/trac/),
which uses Subversion.

> * Still seemed like subversion kept separate version numbers for
> each source file

Not at all.

> (Even though it's say change request 10, and I changed say 2
> files they could have different version numbers depending how
> many times they where changed)


> and I did not see an easy way for the developer and others to
> refer to something that comprised a set of changes.

Just use the revision number (I would like to have symbolic - string -
revision ID but this is another story).

> * Can you with little difficulty recreate (like specify version
> 1.02) from it any version that was delivered from the customer?

Use tags.

> * Does it automatically send messages to approval or other
> parties when things have moved to the next stage like submitted
> for approval, testing completed etc?

See the first question.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Oct 5 15:13:18 2005

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

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