3 ms·

Working for a 15-year old small software company, I converted a whole bunch of ancient CVS stuff (yeah, yeah, don't laugh unless you also have 15 years of profi

Working for a 15-year old small software company, I converted a whole bunch of ancient CVS stuff (yeah, yeah, don't laugh unless you also have 15 years of profitability) to GitLab CE. After a couple of false starts it went flawlessly and now works flawlessly. (I used the tigris.org migration tools). The GitLab team is doing a great job. Thanks you guys.

jobvandervoort 10y ago
Thanks Oliver, that's great to hear. Any way we can prevent those false starts for other people?
- OliverJones 10y ago
  The false starts in our conversion were mostly struggles with how to restructure our old CVS repos so they made sense in the world of git. A few of them had to do with capturing some oddball CVS specific revision and branching history. None of the false starts were due to flaws or confusion in GitLab specifically. I should, and if you pester me I will, sanitize our internal how-to documents and scripts and contribute them to the Gitlab community so the next guy can benefit from our experience.
  - jobvandervoort 10y ago
    Pesters! It would be great to receive some contributions to our documentation. It has proven a big challenge to make sure it covers everything and stays up to date. We'd really appreciate it.
pjc50 10y ago
How about 20+ years of operational history from SCCS: http://fanf.livejournal.com/132656.html http://fanf.livejournal.com/132656.html
SatvikBeri 10y ago
One of the most successful companies I worked at had no version control or unit tests whatsoever. The code was all maintained by one person (the company relied heavily on custom software internally but it wasn't their product), who was able to keep the codebase small enough to basically hold in his head the whole time despite generating millions of dollars of value. That's certainly not how I would write code today, but it is amazing to see how much top-notch programmers vary.

jobvandervoort 10y ago

Thanks Oliver, that's great to hear. Any way we can prevent those false starts for other people?

OliverJones 10y ago
The false starts in our conversion were mostly struggles with how to restructure our old CVS repos so they made sense in the world of git. A few of them had to do with capturing some oddball CVS specific revision and branching history. None of the false starts were due to flaws or confusion in GitLab specifically. I should, and if you pester me I will, sanitize our internal how-to documents and scripts and contribute them to the Gitlab community so the next guy can benefit from our experience.
- jobvandervoort 10y ago
  Pesters! It would be great to receive some contributions to our documentation. It has proven a big challenge to make sure it covers everything and stays up to date. We'd really appreciate it.

pjc50 10y ago

How about 20+ years of operational history from SCCS: http://fanf.livejournal.com/132656.html http://fanf.livejournal.com/132656.html

SatvikBeri 10y ago

One of the most successful companies I worked at had no version control or unit tests whatsoever. The code was all maintained by one person (the company relied heavily on custom software internally but it wasn't their product), who was able to keep the codebase small enough to basically hold in his head the whole time despite generating millions of dollars of value. That's certainly not how I would write code today, but it is amazing to see how much top-notch programmers vary.