- Forum
- General C++ Programming
- Advice on archiving projects.
Advice on archiving projects.
Hello.
I run a small, if not tiny, programming department, which has never had any processes and I am trying to standardize. One thing we've never done well is archiving our projects or custom software libraries we've written.
The current "system" is to simply copy the most current version into a directory on the server. Generally, no one is working on the same thing at the same time. We copy the project down to our individual machines, work on it, and when the project is complete, copy the latest source code up to the server. The server is backed up offsite every night. Our individual machines are backed up to Mozy several times a day.
In this system, older versions of our toolkits or projects are routinely lost, mainly because there is no rule or specification for this. I'm trying to put such things together, but would love advice from the wiser people out there.
I made us an account on Assembla and some of our toolkits are being archived there via Subversion. But is that overkill for 5 guys never working on the same file at the same time?
Any advice, experience, recommendations, recommended books is greatly appreciated. Instead of writing a bad specification, I'd like to just get it (mostly) correct the first time.
As always, thanks in advance.
I run a small, if not tiny, programming department, which has never had any processes and I am trying to standardize. One thing we've never done well is archiving our projects or custom software libraries we've written.
The current "system" is to simply copy the most current version into a directory on the server. Generally, no one is working on the same thing at the same time. We copy the project down to our individual machines, work on it, and when the project is complete, copy the latest source code up to the server. The server is backed up offsite every night. Our individual machines are backed up to Mozy several times a day.
In this system, older versions of our toolkits or projects are routinely lost, mainly because there is no rule or specification for this. I'm trying to put such things together, but would love advice from the wiser people out there.
I made us an account on Assembla and some of our toolkits are being archived there via Subversion. But is that overkill for 5 guys never working on the same file at the same time?
Any advice, experience, recommendations, recommended books is greatly appreciated. Instead of writing a bad specification, I'd like to just get it (mostly) correct the first time.
As always, thanks in advance.
Sounds like you need Team Foundation Server... but it'll cost you. I also recommend looking into CMMI level 2 and 3. While you're organization is small and probably couldn't afford the audit to obtain the certification, there are some principles in general that can be applied in your situation.
Also, you might as well get SharePoint up and running. You may be able to utilize it as well.
It's hard to offer up a precise solution without analyzing your current processes and you DO have processes.
Also, you might as well get SharePoint up and running. You may be able to utilize it as well.
| yetanothertom wrote: |
|---|
| which has never had any processes and I am trying to standardize. |
It's hard to offer up a precise solution without analyzing your current processes and you DO have processes.
Last edited on
Thank you very much!
You're right; we don't need to be audited, but that doesn't mean I don't want to be doing things the proper way.
I've only used SVN servers, never Team Foundation. What's the advantages?
>> and you DO have processes.
I suppose, but not very consistent or comprehensive ones.
You're right; we don't need to be audited, but that doesn't mean I don't want to be doing things the proper way.
I've only used SVN servers, never Team Foundation. What's the advantages?
>> and you DO have processes.
I suppose, but not very consistent or comprehensive ones.
Topic archived. No new replies allowed.