Stephane Bortzmeyer wrote:
>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)
>>
>>
>
>Wrong.
>
This is what let me to this conclution. From the Basic Concepts and
Tags section of the online book.
"$ svn commit button.c
Sending button.c
Transmitting file data .
Committed revision 57."
and
"However, people often want to give more human-friendly names to tags,
like release-1.0. And they want to make snapshots of smaller
subdirectories of the filesystem. After all, it's not so easy to
remember that release-1.0 of a piece of software is a particular
subdirectory of revision 4822."
Just seemed like when I submitted I was submitting autonomous files and
not anything at a higher level of some change request. But given your
other answer above you would not expect it to as it's just a versioning
of files not necessarily built to help you manage change at a higher
level like a bug fix and all the change that entailed, at least not by
itself or with great ease. You need some other shell around it.
>
>
>
>> 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.
>
I looked at this briefly. It is just a copy it seems. So your not for
say working on release 2.3 (at least from a SuBVersion perspective)
while your submitting but you create a release once you say ok looks
good tag it!
How Would this work if I needed to work on 2 versions simultaneously?
Can I keep chnages separate between the versions some how? I guess you
create a separate branch? Do the changes get propagated from one
release to the next? I know some manual intervention in enviable if
massive chnages.
>
>
>
>> * 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.
>
i.e. No no in scope correct?
Thanks was just trying to see what it is and is not. This helped a lot!!!
>
>
>
>
>
Received on Wed Oct 5 16:14:45 2005