Project files management (was Re: Welcome)
joerg at openmoko.org
Mon Apr 20 16:04:35 CEST 2009
Am Mo 20. April 2009 schrieb Lothar Behrens:
> But I have another issue I ran in a company:
> The company handled that with a schematics file and board file for
> each version. Adding those
> files to a version control system is a nightmare, but I tend to argue
> to use version control systems.
> The company made the error to make backups to another directory, thus
> the number of project files
> are much more than the existing versions.
> I think, when publishing files only this will become the same. Using
> PDF files for reference only is no problem, but ...
> How do you manage versions of boards and schematics?
> Could board names or schematic names (version included) renamed
> without renaming the files (CVS/SVN will be a trouble)?
> How do you manage the feedback (subprojects) of schematic changes,
> when done in different files (copies)?
> (That was the problem in the company. 'Where was the change for this
> customer, ehh that issue?')
Yes, all these topics are poorly supported in all CAE-programs I know of.
Especially merge of subprojects is virtually impossible in any reasonable way.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 197 bytes
Desc: This is a digitally signed message part.
Url : http://lists.openmoko.org/pipermail/gta03/attachments/20090420/cc9d70c3/attachment.pgp
More information about the Gta03