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

real quick answers about Subversion

From: Frank <fgeck_at_optonline.net>
Date: 2005-10-05 14:39:51 CEST

I was wondering if some of you could help me out real quick to get some
real quick answers about Subversion. I don't have the time to do a
full-blown evaluation need to get something to some one like tomorrow on
what Subversion does and doesn't do.


It looks like Subversions is a good basic way to keep multiple
developers from over laying code. But I did not see a lot or a way
easily to so some of the following:


    * Refer to a bunch of developer changes by some name (i.e. change
      request). Has this change sets but seemed real clumsy

    * 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. Ok this change request
      changed all these files, with some text explanation in the system
      detailing the changes along the way. It was submitted at some date
      by the developer. It then accepted or rejected approved by some
      other party. Then some tester uses Subversion to get a set of
      change request or maybe just one to unit test then maybe System
      test. Then eventually approved by the tester to move into some
      official version, or even various test levels like a unit test and
      system test states.

    * Still seemed like subversion kept separate version numbers
      for each source file (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.

    * Can you with little difficulty recreate (like specify version
      1.02) from it any version that was delivered from the customer?
      Or is it like others you better make a special archive of it?

    * 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?

If you had the money would you still use Subversion or are there much
better commercial products out there? PVCS I found to be quite lame
SubVersion is probably just as good. The best that I have ever used is
Sablime to date. Any other thoughts?


Received on Wed Oct 5 14:44:08 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.