On Nov 7, 9:11 am, sstadler <sstad..._at_incircuits.com> wrote:
> I am trying to figure out how to use some of the tools I have to get some
> level of configuration management into a plan and process.....
>
> I want to make a collection of files, including schematic file, pcb file,
> BOM, software, calculations, etc. as a released version of those files.
>
> When using Tortoise SVN with Subversion, I made a tag for my software file,
> which makes a folder in the repository, but not in the file manager, and I
> couldn't select another file and make a tag using the same tag folder in the
> repository. So, I went into the repo-browser and browsed the tag folder in
> the repository, and right clicked to add a file, and I added the files to
> make the collection I want.
>
> Now I have a tag folder in the project repository named version_1.0.0.0 that
> has a collection of files each with their unique version number.
>
> Is this the proper way to put a collection of files together as a Release /
> Tag in Subversion using TortoiseSVN??
>
> Thank You,
>
> Steve
> --
>
Steve,
That is a great question. I am looking at TSVN as a DMS for
engineering documents and have a similar concern over making a record
of different types of document issue / publications. If a folder is
made that will never be revised, can it contain links to folders/files
of differing revisions. Apparently that is part of what tags do but I
have not fully comprehended this yet. How will control over this
folder be managed. If it is needed to share the contents of this
folder across the world with some types of rights, what are some
different methods to expose this data to the world? Should the method
me any different if only internal issuing is necessary?
Internal distribution of documents has additional opportunities. When
files are sent out for others to review, what are some methods to
expose the documents to be reviewed, collect comments, group review
comments and final document reconciliation?
A similar concern comes in when supplier/manufacturer data comes again
that is supposed to satisfy a purchase order (PO) specification
requirement. When such data comes in, the person responsible for the
requisitioning of that material must look to assure that the documents
actually relate to the subject PO. Everyone that needs to either know
that the data has come in or must review the data need to receive
information about its location. Similar to the previous review, all
review comments must be collected, the comments must undergo a group
review, the comments must be consolidated and a final disposition/mark-
up of the received data must be returned to the supplier.
Additionally, all the requirements that are associated with a PO must
be available so reviewers know what to check against. There should be
a systematic way to verify that the PO specs are met by the received
documents. If marked-up documents are sent back to the suppler, when
those documents are returned, they become part of the basis to verify
the new documents so they must be made easily available.
It would be handy if there was a check sheet (XML?) that came along
with documents that need to be reviewed that pointed to reference
documents.
Since this process is repeated many times for different POs on a
project and from project to project, it would be handy to have one or
more templates that could be reused that included the appropriate
access rights and linkages to help smooth out the whole process and
make it repeatable. Maybe even a form that could be filled out with
typical file structures and access rights so a new project could be
started with a script.
Ray
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-11-07 21:55:17 CET